Triple
T34474980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalingei |
E885006
|
entity |
| Predicate | hasReliefAgencyPresence |
P60496
|
FINISHED |
| Object | United Nations |
E340
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: United Nations | Statement: [Zalingei, hasReliefAgencyPresence, United Nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefAgencyPresence Context triple: [Zalingei, hasReliefAgencyPresence, United Nations]
-
A.
reliefOrganization
Indicates that an entity is an organization whose primary role is to provide aid, assistance, or relief in response to emergencies, disasters, or humanitarian needs.
-
B.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
-
C.
hasHumanitarianPresence
chosen
Indicates that a humanitarian organization or effort is present and actively operating in relation to the referenced entity.
-
D.
hasRescueServices
Indicates that one entity provides or is equipped with rescue or emergency response services for another entity or area.
-
E.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
- F. None of above.
Provenance (4 batches)
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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a372129c02c819099164b1def272da5 |
completed | June 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.