Triple
T4784812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butembo Health Zone |
E106449
|
entity |
| Predicate | locatedInConflictRegion |
P21190
|
FINISHED |
| Object | Kivu conflict area |
—
|
LITERAL 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: Kivu conflict area | Statement: [Butembo Health Zone, locatedInConflictRegion, Kivu conflict area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInConflictRegion Context triple: [Butembo Health Zone, locatedInConflictRegion, Kivu conflict area]
-
A.
conflictRegion
chosen
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
B.
conflictLocation
Indicates the place or geographic area where a conflict, dispute, or confrontation occurs or is centered.
-
C.
locatedInDisputedTerritory
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
-
D.
formedInConflict
Indicates that an entity came into existence as a direct result of, or during the course of, a specific conflict or war.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- F. None of above.
Provenance (3 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.