Triple
T11888199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kel Air |
E282844
|
entity |
| Predicate | associatedDesertRoute |
P102074
|
FINISHED |
| Object | trans-Saharan caravan routes |
—
|
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: trans-Saharan caravan routes | Statement: [Kel Air, associatedDesertRoute, trans-Saharan caravan routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDesertRoute Context triple: [Kel Air, associatedDesertRoute, trans-Saharan caravan routes]
-
A.
traversesDesert
Indicates that an entity moves across or through a desert region, typically implying a journey over arid terrain.
-
B.
hasNearbyDesert
Indicates that one entity is located close to or in the vicinity of a desert region associated with another entity.
-
C.
isLocatedInDesert
Indicates that something exists or is situated within a desert region or environment.
-
D.
desertsFrom
Indicates that an entity abandons or leaves allegiance to another entity, typically in a disloyal or unauthorized manner.
-
E.
linkedDesertToNorth
Indicates a relationship where one entity connects or associates a desert with a northern direction or northern region.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a2860c8190a21af5fcddbd2f1e |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.