Triple
T28620460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA 178 |
E724367
|
entity |
| Predicate | hasDesertHighwaySegmentIn |
P80869
|
FINISHED |
| Object | Mojave Desert |
—
|
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: Mojave Desert | Statement: [CA 178, hasDesertHighwaySegmentIn, Mojave Desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesertHighwaySegmentIn Context triple: [CA 178, hasDesertHighwaySegmentIn, Mojave Desert]
-
A.
associatedDesertRoute
Indicates a relationship where an entity is linked to, or connected with, a specific desert route, such as a path, trail, or corridor through a desert region.
-
B.
isLocatedInDesert
Indicates that something exists or is situated within a desert region or environment.
-
C.
hasNearbyDesert
Indicates that one entity is located close to or in the vicinity of a desert region associated with another entity.
-
D.
hasFreewaySegments
chosen
Indicates that one entity includes, contains, or is associated with specific freeway segments as part of its structure or network.
-
E.
highwaySegment
Indicates a road section that forms part of a larger highway route.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 4:33 a.m.