Triple
T36862362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Darfur |
E910976
|
entity |
| Predicate | hasDisplacementTo |
P85504
|
FINISHED |
| Object | Chad |
—
|
NE NERFINISHED |
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: Chad | Statement: [West Darfur, hasDisplacementTo, Chad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplacementTo Context triple: [West Darfur, hasDisplacementTo, Chad]
-
A.
hasDisplacement
chosen
Indicates a relationship where an entity experiences or is assigned a change in position or location from an initial point to a final point.
-
B.
hasDisplacementType
Indicates the specific kind or category of displacement associated with an entity or process.
-
C.
hasMaxDisplacement
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
-
D.
introducedWithDisplacement
Indicates that one entity was introduced or brought into a context or environment while simultaneously causing the removal, replacement, or displacement of another entity.
-
E.
displacementOccurred
Indicates that an entity has been moved from its original position or location to a different one.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.