Triple
T34901629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arua District |
E1006605
|
entity |
| Predicate | locatedInSubRegion |
P77476
|
FINISHED |
| Object | West Nile sub-region |
E810858
|
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: West Nile sub-region | Statement: [Arua District, locatedInSubRegion, West Nile sub-region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSubRegion Context triple: [Arua District, locatedInSubRegion, West Nile sub-region]
-
A.
isInSubregion
chosen
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
B.
isLocatedInSubdivision
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
-
C.
refersToPlaceInSubregion
Indicates that something makes reference to a place that is located within a specific subregion of a larger area.
-
D.
hasSubregionRole
Indicates that an entity holds a specific role, function, or status within a defined subregion of a larger area or jurisdiction.
-
E.
hasSubregionRelationWith
Indicates a relationship where one region is a subregion or contained part of another region.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8adc2988190a8eed1fe1ee53c2d |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.