Triple
T36862340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Darfur |
E910976
|
entity |
| Predicate | geographicalDirectionInSudan |
P192680
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [West Darfur, geographicalDirectionInSudan, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalDirectionInSudan Context triple: [West Darfur, geographicalDirectionInSudan, west]
-
A.
primaryLocationInSudan
Indicates that the primary or main location associated with an entity is situated within the country of Sudan.
-
B.
directionFromCairo
Indicates the cardinal or relative compass direction of an entity’s location measured from Cairo.
-
C.
populationRankInSudan
Indicates the relative position of an entity in terms of population size compared to other entities within Sudan.
-
D.
directionFromMogadishu
Indicates the cardinal or relative direction in which one entity is located when measured from Mogadishu as the point of reference.
-
E.
locatedInDirectionWithinEgypt
Indicates that one place is situated in a specified cardinal or relative direction from another place, with both locations being within the borders of Egypt.
- F. None of above. chosen
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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.