Triple
T30587963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 66 |
E778568
|
entity |
| Predicate | connectsWithHighway |
P12245
|
FINISHED |
| Object | Interstate 30 |
—
|
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: Interstate 30 | Statement: [Texas State Highway 66, connectsWithHighway, Interstate 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithHighway Context triple: [Texas State Highway 66, connectsWithHighway, Interstate 30]
-
A.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
motorwayConnectionWith
Indicates that two locations are directly connected by a motorway, allowing vehicular travel between them via that road.
-
C.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
E.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 29, 2026, 8:24 p.m.