Triple
T12809588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burundian Civil War |
E306234
|
entity |
| Predicate | refugeeOutflow |
P94592
|
FINISHED |
| Object | refugees to Tanzania |
—
|
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: refugees to Tanzania | Statement: [Burundian Civil War, refugeeOutflow, refugees to Tanzania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refugeeOutflow Context triple: [Burundian Civil War, refugeeOutflow, refugees to Tanzania]
-
A.
hasRefugeeMovements
chosen
Indicates that there are movements or flows of refugees involving the related entities, such as people fleeing from one place and arriving in another.
-
B.
hasRefugeePopulation
Indicates that an entity hosts, contains, or is associated with a population of refugees.
-
C.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
D.
refugeeAdministration
Indicates the management, coordination, or oversight of services, policies, and procedures related to refugees.
-
E.
estimatedEmigrants
Indicates the estimated number of people who have left a place or country to live elsewhere.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e817598819080fdd61e9d61236e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.