Triple
T27406338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 84 |
E692009
|
entity |
| Predicate | connectsToHighwayAtWesternTerminus |
P51120
|
FINISHED |
| Object | Interstate 5 |
—
|
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 5 | Statement: [Interstate 84, connectsToHighwayAtWesternTerminus, Interstate 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToHighwayAtWesternTerminus Context triple: [Interstate 84, connectsToHighwayAtWesternTerminus, Interstate 5]
-
A.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
C.
hasTerminusWest
chosen
Indicates that something has its western endpoint, terminus, or final stop at the referenced entity.
-
D.
hasRoadTerminus
Indicates that one location or road segment serves as an endpoint or terminus for a particular road.
-
E.
atJunctionOf
Indicates that something is located at or directly connected to the point where two or more paths, roads, or lines meet.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 12:30 p.m.