Triple
T4420873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian Data Exchange |
E95093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian data platform |
C5235
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: humanitarian data platform Context triple: [Humanitarian Data Exchange, instanceOf, humanitarian data platform]
-
A.
policy-relevant data compendium
A policy-relevant data compendium is a curated, structured collection of datasets and indicators organized to inform, support, and evaluate public policy decisions on specific issues or sectors.
-
B.
United Nations information system
A United Nations information system is an integrated framework of technologies, databases, and processes used across UN entities to collect, manage, analyze, and disseminate data and knowledge in support of the organization’s mandates and decision-making.
-
C.
humanitarian emblem
A humanitarian emblem is a universally recognized protective symbol used in armed conflicts and emergencies to identify and safeguard medical services, relief personnel, and facilities under international humanitarian law.
-
D.
open data platform
chosen
An open data platform is a system that collects, manages, and publishes structured datasets with standardized formats and open access policies, enabling users to discover, download, and reuse data freely.
-
E.
Carter Center program
A Carter Center program is an organized initiative led by The Carter Center that applies targeted strategies, partnerships, and resources to advance peace, health, and human rights in specific regions or issue areas.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:30 p.m.