doc_id stringlengths 16 27 | page int64 0 3.45k | chunk int64 0 38 | mention_name stringlengths 2 86 | start int64 0 2.75k | end int64 4 2.78k | extractor_specificity stringclasses 3
values | extractor_typology stringclasses 1
value | specificity stringclasses 3
values | typology stringclasses 11
values | usage stringlengths 0 1.45k ⌀ | valid_data_mention bool 2
classes | judge_error stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
jdc_operational:000055 | 35 | 1 | LQAS surveys | 1,168 | 1,180 | named | named | survey | as well quarterly ⟦LQAS surveys⟧[22] (activity (f)) nationwide | true | null | |
jdc_operational:000055 | 40 | 1 | MoH Health Management Information Systems | 826 | 867 | named | named | system | the MoH has been able to build its county monitoring system and produce monthly and annual ⟦MoH Health Management Information Systems⟧[23] (HMIS) reports. | true | null | |
jdc_operational:000055 | 41 | 1 | special surveys | 1,194 | 1,209 | descriptive | descriptive | survey | using the BHI initiative to ensure citizen voices are heard and incorporated in service delivery, and ⟦special surveys⟧[24] to capture community feedback. | true | null | |
jdc_operational:000055 | 46 | 0 | facility reports | 765 | 781 | descriptive | descriptive | administrative | Routine monthly and quarterly data collected via ⟦facility reports⟧[25] that will be aggregated for the project’s quarterly and annual indicators | true | null | |
jdc_operational:000055 | 46 | 1 | LQAS surveys | 313 | 325 | named | named | survey | ⟦LQAS surveys⟧[26] to measure population coverage of health services | true | null | |
jdc_operational:000055 | 46 | 1 | HMIS | 608 | 612 | named | named | system | All routine health interventions supported by the project will use the ⟦HMIS⟧[27] | true | null | |
jdc_operational:000055 | 46 | 1 | DHIS2 | 637 | 642 | named | named | system | to the extent possible ⟦DHIS2⟧[28] | true | null | |
jdc_operational:000055 | 46 | 1 | national health management information system | 939 | 984 | descriptive | descriptive | system | The data for monitoring will come from: (i) the ⟦national health management information system⟧[29] (HMIS/DHIS2) | true | null | |
jdc_operational:000055 | 46 | 2 | project data | 308 | 320 | vague | vague | other | monitor the health system’s performance through ⟦project data⟧[30], progress narratives and monitoring reports. | true | null | |
jdc_operational:000055 | 47 | 0 | health service availability data | 1,092 | 1,124 | descriptive | vague | other | monitor ⟦health service availability data⟧ in accessible areas | true | null | |
jdc_operational:000055 | 47 | 0 | health service functionality data | 1,971 | 2,004 | descriptive | vague | other | the results of ⟦health service functionality data⟧ will be presented and discussed | true | null | |
jdc_operational:000055 | 47 | 1 | health service functionality data | 22 | 55 | descriptive | vague | other | where the results of ⟦health service functionality data⟧ will be presented and discussed | true | null | |
jdc_operational:000055 | 47 | 1 | master health service functionality database | 1,826 | 1,870 | descriptive | descriptive | database | Creation of a ⟦master health service functionality database⟧, capturing development and humanitarian health services across donors | true | null | |
jdc_operational:000055 | 47 | 2 | master health service functionality database | 96 | 140 | descriptive | descriptive | database | Creation of a ⟦master health service functionality database⟧, capturing development and humanitarian health services across donors | true | null | |
jdc_operational:000055 | 48 | 0 | health service functionality database | 552 | 589 | descriptive | descriptive | database | merge the respective datasets into one, definitive ⟦health service functionality database⟧ | true | null | |
jdc_operational:000055 | 48 | 0 | DHIS2 | 714 | 719 | named | named | system | this database will be linked to ⟦DHIS2⟧ | true | null | |
jdc_operational:000055 | 48 | 0 | routine data collected from implementing partners | 1,647 | 1,696 | descriptive | descriptive | other | Based on the ⟦routine data collected from implementing partners⟧ and the verification visits | true | null | |
jdc_operational:000055 | 48 | 1 | population figures | 402 | 420 | descriptive | descriptive | other | These data elements, combined with ⟦population figures⟧, will enable the system to compute | true | null | |
jdc_operational:000055 | 48 | 1 | health service functionality data | 1,118 | 1,151 | descriptive | vague | other | technical review of ⟦health service functionality data⟧ with development and humanitarian stakeholders | true | null | |
jdc_operational:000055 | 48 | 1 | LQAS surveys | 1,816 | 1,828 | named | descriptive | survey | National ⟦LQAS surveys⟧ will be conducted with the aim of producing information | true | null | |
jdc_operational:000055 | 48 | 2 | LQAS | 36 | 40 | named | named | other | The ⟦LQAS⟧ will also be used to estimate coverage proportions at state level | false | null | |
jdc_operational:000055 | 49 | 0 | routine programmatic data | 1,307 | 1,332 | descriptive | descriptive | other | triangulation of ⟦routine programmatic data⟧ (results indicators) | true | null | |
jdc_operational:000055 | 49 | 0 | georeferenced data | 1,355 | 1,373 | descriptive | descriptive | geospatial | ⟦georeferenced data⟧ on service delivery and delivery of commodities | true | null | |
jdc_operational:000055 | 49 | 0 | Data from ICRC programs or assessments | 1,657 | 1,695 | descriptive | descriptive | other | ⟦Data from ICRC programs or assessments⟧ collected in the field are sent back to a central office location | true | null | |
jdc_operational:000055 | 49 | 1 | ICRC GPS data logs | 1,719 | 1,737 | named | named | geospatial | Provision of the ⟦ICRC GPS data logs⟧ of its vehicles | true | null | |
jdc_operational:000055 | 50 | 0 | national health information system | 2,084 | 2,118 | descriptive | descriptive | system | contribute the ⟦national health information system⟧ as well as strengthening alignment | true | null | |
jdc_operational:000055 | 51 | 0 | data from the project | 782 | 803 | vague | vague | other | learning from ⟦data from the project⟧ that will contribute to health sector policies | true | null | |
jdc_operational:000055 | 61 | 0 | project file | 1,050 | 1,062 | descriptive | descriptive | other | recorded and documented in the ⟦project file⟧ | true | null | |
jdc_operational:000055 | 61 | 1 | register of losses, incidents and fraud | 311 | 350 | descriptive | descriptive | administrative | a ⟦register of losses, incidents and fraud⟧ reported by IPs was introduced | true | null | |
jdc_operational:000055 | 63 | 1 | Transparency International 2017 corruption perception index | 1,744 | 1,803 | named | named | indicator | ranked 179/180 by ⟦Transparency International 2017 corruption perception index⟧ | true | null | |
jdc_operational:000055 | 63 | 1 | 2017 Ibrahim Index of African governance | 1,825 | 1,865 | named | named | indicator | ranked 53/54 by the ⟦2017 Ibrahim Index of African governance⟧ | true | null | |
jdc_operational:000055 | 63 | 2 | Transparency International 2017 corruption perception index | 44 | 103 | named | named | indicator | ranked 179/180 by ⟦Transparency International 2017 corruption perception index⟧ | true | null | |
jdc_operational:000055 | 63 | 2 | 2017 Ibrahim Index of African governance | 125 | 165 | named | named | indicator | ranked 53/54 by the ⟦2017 Ibrahim Index of African governance⟧ | true | null | |
jdc_operational:000055 | 69 | 0 | PDO Indicators | 1,145 | 1,159 | named | descriptive | other | ⟦PDO Indicators⟧ Datasource | false | null | |
jdc_operational:000055 | 69 | 1 | health facility registers | 393 | 418 | descriptive | descriptive | administrative | be collected from ⟦health facility registers⟧ | true | null | |
jdc_operational:000055 | 69 | 1 | DHIS2 database | 464 | 478 | named | named | database | and ⟦DHIS2 database⟧ | true | null | |
jdc_operational:000055 | 70 | 0 | health facility registers | 441 | 466 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[1] and ⟦DHIS2 database⟧[2]. | true | null | |
jdc_operational:000055 | 70 | 0 | DHIS2 database | 474 | 488 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[1] and ⟦DHIS2 database⟧[2]. | true | null | |
jdc_operational:000055 | 70 | 0 | health facility registers | 676 | 701 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[3] | true | null | |
jdc_operational:000055 | 70 | 0 | health facility registers | 1,001 | 1,026 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[4] | true | null | |
jdc_operational:000055 | 70 | 1 | DHIS2 database | 94 | 108 | named | named | database | and ⟦DHIS2 database⟧[5]. | true | null | |
jdc_operational:000055 | 71 | 0 | health facility registers | 274 | 299 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[6] and ⟦DHIS2 database⟧[7]. | true | null | |
jdc_operational:000055 | 71 | 0 | DHIS2 database | 307 | 321 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[6] and ⟦DHIS2 database⟧[7]. | true | null | |
jdc_operational:000055 | 71 | 0 | health facility registers | 749 | 774 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[8] and DHIS2 database. | true | null | |
jdc_operational:000055 | 71 | 1 | health facility registers | 148 | 173 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[9] and ⟦DHIS2 database⟧[10]. | true | null | |
jdc_operational:000055 | 71 | 1 | DHIS2 database | 181 | 195 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[9] and ⟦DHIS2 database⟧[10]. | true | null | |
jdc_operational:000055 | 71 | 1 | health facility registers | 600 | 625 | descriptive | descriptive | administrative | be collected from ⟦health facility registers⟧[11] and DHIS2 database. | true | null | |
jdc_operational:000055 | 72 | 1 | health facility registers | 140 | 165 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[12] | true | null | |
jdc_operational:000055 | 72 | 1 | DHIS2 database | 379 | 393 | named | named | database | and ⟦DHIS2 database⟧[13]. | true | null | |
jdc_operational:000055 | 73 | 0 | health facility registers | 494 | 519 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[14] and ⟦DHIS2 database⟧[15]. | true | null | |
jdc_operational:000055 | 73 | 0 | DHIS2 database | 527 | 541 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[14] and ⟦DHIS2 database⟧[15]. | true | null | |
jdc_operational:000055 | 73 | 0 | health facility registers | 867 | 892 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[16] | true | null | |
jdc_operational:000055 | 73 | 1 | DHIS2 database | 40 | 54 | named | named | database | and ⟦DHIS2 database⟧[17]. | true | null | |
jdc_operational:000055 | 74 | 0 | health facility registers | 583 | 608 | descriptive | descriptive | administrative | Data on indicator will be collected from ⟦health facility registers⟧[18], ⟦DHIS2 database⟧[19] and ⟦BHI database⟧[20]. | true | null | |
jdc_operational:000055 | 74 | 0 | DHIS2 database | 613 | 627 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[18], ⟦DHIS2 database⟧[19] and ⟦BHI database⟧[20]. | true | null | |
jdc_operational:000055 | 74 | 0 | BHI database | 635 | 647 | named | named | database | Data on indicator will be collected from ⟦health facility registers⟧[18], ⟦DHIS2 database⟧[19] and ⟦BHI database⟧[20]. | true | null | |
jdc_operational:000055 | 75 | 0 | DHIS2 database | 282 | 296 | named | named | database | and ⟦DHIS2 database⟧[21]. | true | null | |
jdc_operational:000055 | 76 | 0 | DHIS2 | 747 | 752 | named | named | database | crosschecked in ⟦DHIS2⟧[22] or equivalent database. | true | null | |
jdc_operational:000055 | 87 | 0 | ICRC chart of accounts | 1,236 | 1,258 | named | named | other | specific expenditure categories from ⟦ICRC chart of accounts⟧[23] were identified and agreed upon. | false | null | |
jdc_operational:000056 | 1 | 0 | PROJECT FINANCING DATA | 637 | 659 | descriptive | vague | other | ### **⟦PROJECT FINANCING DATA⟧[24] (US$, Millions)** | false | null | |
jdc_operational:000056 | 3 | 0 | Human Capital Index | 96 | 115 | named | named | indicator | Results of the recently launched ⟦Human Capital Index⟧[25], which is a measure of human productivity, showed low results | true | null | |
jdc_operational:000057 | 11 | 1 | high frequency data | 680 | 699 | vague | vague | other | However, ⟦high frequency data⟧[26] indicate that food prices started increasing in February 2022. | true | null | |
jdc_operational:000057 | 12 | 1 | Climate Change Vulnerability Index | 1,260 | 1,294 | named | named | indicator | South Sudan ranked among the five worst-performing countries in the world in tackling the impact of climate change, according to the ⟦Climate Change Vulnerability Index⟧[27]. | true | null | |
jdc_operational:000057 | 13 | 0 | data provided by the Global Network Against Food Crises | 209 | 264 | named | descriptive | other | _Source: Developed from ⟦data provided by the Global Network Against Food Crises⟧[28] and IPC_ | true | null | |
jdc_operational:000057 | 14 | 0 | Human Capital Index | 190 | 209 | named | named | indicator | South Sudan ranked 172 out of 174 in the ⟦Human Capital Index⟧[29] (HCI) in 2020, with HCI at 0.31 | true | null | |
jdc_operational:000057 | 14 | 2 | Human Capital Index 2020 | 663 | 687 | named | named | other | See _World Bank. 2020. ⟦Human Capital Index 2020⟧[30]._ | false | null | |
jdc_operational:000057 | 15 | 2 | Refugee and Asylum Seeker Population | 553 | 589 | named | named | report | South Sudan: ⟦Refugee and Asylum Seeker Population⟧, UNHCR, 31 December 2021 | true | null | |
jdc_operational:000057 | 17 | 0 | robust data on coverage | 1,866 | 1,889 | vague | vague | other | While ⟦robust data on coverage⟧ do not exist | false | null | |
jdc_operational:000057 | 20 | 0 | integrated biometric and Management Information System | 1,699 | 1,753 | named | named | system | Percentage of beneficiaries paid using the ⟦integrated biometric and Management Information System⟧ (MIS) | true | null | |
jdc_operational:000057 | 23 | 0 | MIS | 1,168 | 1,171 | named | named | system | the list of beneficiaries will be generated from the ⟦MIS⟧ | true | null | |
jdc_operational:000057 | 23 | 0 | MIS | 1,177 | 1,180 | named | named | system | The ⟦MIS⟧ will capture beneficiaries' ⟦biometric data⟧ | true | null | |
jdc_operational:000057 | 23 | 0 | biometric data | 1,209 | 1,223 | descriptive | descriptive | other | The ⟦MIS⟧ will capture beneficiaries' ⟦biometric data⟧ | true | null | |
jdc_operational:000057 | 25 | 0 | diagnostic of the South Sudan SP sector | 1,799 | 1,838 | descriptive | descriptive | other | A ⟦diagnostic of the South Sudan SP sector⟧ undertaken by the World Bank found that majority of the safety net interventions in the country tend to include work requirements | false | null | |
jdc_operational:000057 | 25 | 1 | diagnostic of the South Sudan SP sector | 4 | 43 | descriptive | descriptive | other | A ⟦diagnostic of the South Sudan SP sector⟧ undertaken by the World Bank found that majority of the safety net interventions in the country tend to include work requirements | false | null | |
jdc_operational:000057 | 30 | 1 | SSSNP caseload | 1,053 | 1,067 | named | descriptive | other | 65,000 will continue to be from the ⟦SSSNP caseload⟧ | false | null | |
jdc_operational:000057 | 35 | 0 | preliminary findings from SSSNP | 1,110 | 1,141 | named | descriptive | other | ⟦preliminary findings from SSSNP⟧ suggest that the number of HHs that saved increased by 13 percentage points | false | null | |
jdc_operational:000057 | 39 | 0 | Registration Lessons Learned surveys | 965 | 1,001 | descriptive | named | survey | Key M&E activities will include ⟦Registration Lessons Learned surveys⟧ that will assess the effectiveness of targeting and registration | true | null | |
jdc_operational:000057 | 42 | 1 | gender-disaggregated data | 1,182 | 1,207 | descriptive | descriptive | other | all M&E activities will employ ⟦gender-disaggregated data⟧ to monitor the participation and performance of female beneficiaries | true | null | |
jdc_operational:000057 | 44 | 2 | Flagship Survey | 356 | 371 | named | named | survey | UNHCR has recently initiated a ‘⟦Flagship Survey⟧’ that will provide rich new data on the socioeconomic conditions of refugees and hosts in South Sudan | true | null | |
jdc_operational:000057 | 45 | 0 | World Bank staff estimates | 661 | 687 | descriptive | named | estimates | _Source:_ ⟦World Bank staff estimates⟧ | true | null | |
jdc_operational:000057 | 50 | 1 | 2021 Corruption Perception Index | 1,398 | 1,430 | named | named | indicator | The ⟦2021 Corruption Perception Index⟧ ranked the country as most corrupt | true | null | |
jdc_operational:000057 | 55 | 0 | beneficiary data | 559 | 575 | descriptive | descriptive | administrative | The implementing partner will collect ⟦beneficiary data⟧ during targeting and registration | true | null | |
jdc_operational:000057 | 55 | 0 | payment data | 807 | 819 | descriptive | descriptive | administrative | the payment service provider will document ⟦payment data⟧ and share with the implementing partner | true | null | |
jdc_operational:000057 | 55 | 1 | beneficiary data | 92 | 108 | descriptive | descriptive | administrative | The implementing partner will collect ⟦beneficiary data⟧ during targeting and registration | true | null | |
jdc_operational:000057 | 56 | 0 | beneficiary data | 630 | 646 | vague | descriptive | administrative | ⟦beneficiary data⟧ during targeting and registration | true | null | |
jdc_operational:000057 | 56 | 0 | payment data | 739 | 751 | vague | descriptive | administrative | The payment service provider will collect ⟦payment data⟧ and share with the implementing partner | true | null | |
jdc_operational:000057 | 57 | 0 | satisfaction surveys | 491 | 511 | descriptive | descriptive | survey | and ⟦satisfaction surveys⟧ carried out by the SNSOP M&E team | true | null | |
jdc_operational:000057 | 57 | 1 | SNSOP MIS | 354 | 363 | named | named | system | Data on payment of the livelihood grant will be collected through the ⟦SNSOP MIS⟧ that will be linked with SNSOP payment data | true | null | |
jdc_operational:000057 | 58 | 0 | Monitoring Surveys | 685 | 703 | descriptive | descriptive | survey | ⟦Monitoring Surveys⟧ carried out by the M&E team | true | null | |
jdc_operational:000057 | 59 | 0 | Payments data | 835 | 848 | descriptive | descriptive | administrative | Registration and ⟦Payments data⟧ will be obtained from the project MIS | true | null | |
jdc_operational:000057 | 60 | 0 | Payment data | 305 | 317 | vague | descriptive | administrative | ⟦Payment data⟧ will be liked to and updated in the MIS | true | null | |
jdc_operational:000057 | 60 | 0 | SNSOP MIS | 812 | 821 | named | named | system | Registration and payment data in the ⟦SNSOP MIS⟧ | true | null | |
jdc_operational:000057 | 60 | 1 | Attendance data | 406 | 421 | descriptive | descriptive | administrative | ⟦Attendance data⟧ collected during each training session | true | null | |
jdc_operational:000057 | 60 | 1 | Beneficiary data | 529 | 545 | descriptive | descriptive | administrative | ⟦Beneficiary data⟧ will be collected during registration and updated over the course of project implementation | true | null | |
jdc_operational:000057 | 61 | 0 | SNSOP MIS | 249 | 258 | named | named | system | Payment data will be regularly updated in the ⟦SNSOP MIS⟧ | true | null | |
jdc_operational:000057 | 61 | 1 | Beneficiary data | 646 | 662 | descriptive | descriptive | administrative | ⟦Beneficiary data⟧ is collected during registration | true | null | |
jdc_operational:000057 | 62 | 0 | SNSOP MIS | 693 | 702 | named | named | system | ⟦SNSOP MIS⟧ updated over the course of the project | true | null | |
jdc_operational:000057 | 62 | 0 | Payment data | 749 | 761 | vague | descriptive | other | ⟦Payment data⟧ will also be periodically updated in the MIS | true | null | |
jdc_operational:000057 | 62 | 0 | Beneficiary data | 1,218 | 1,234 | vague | vague | other | ⟦Beneficiary data⟧ will be | true | null | |
jdc_operational:000057 | 62 | 1 | SNSOP MIS | 24 | 33 | named | named | system | ⟦SNSOP MIS⟧ | true | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.