Triple
T9804100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chad |
E237909
|
entity |
| Predicate | northernRegionAdjacentTo |
P90062
|
FINISHED |
| Object | Fezzan (Libya) via Tibesti Mountains |
—
|
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: Fezzan (Libya) via Tibesti Mountains | Statement: [Chad, northernRegionAdjacentTo, Fezzan (Libya) via Tibesti Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernRegionAdjacentTo Context triple: [Chad, northernRegionAdjacentTo, Fezzan (Libya) via Tibesti Mountains]
-
A.
northTerminusRegion
Indicates that a specified region serves as the northern endpoint or terminus of a linear feature, route, or entity.
-
B.
northernTerminusRegion
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
-
C.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
D.
northernPartKnownAs
Indicates that the northern portion of an entity is referred to by a particular name or designation.
-
E.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7a0ce881908f0555d194dece3f |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:29 p.m.