Triple
T29397154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sepulveda Pass |
E745529
|
entity |
| Predicate | hasNearbyFreewayInterchange |
P33739
|
FINISHED |
| Object | U.S. Route 101 and I-405 interchange |
—
|
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: U.S. Route 101 and I-405 interchange | Statement: [Sepulveda Pass, hasNearbyFreewayInterchange, U.S. Route 101 and I-405 interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFreewayInterchange Context triple: [Sepulveda Pass, hasNearbyFreewayInterchange, U.S. Route 101 and I-405 interchange]
-
A.
hasNearbyInterchange
chosen
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
-
B.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
C.
nearestInterstateExit
Indicates the relationship where a given location is associated with the closest interstate highway exit to it.
-
D.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
E.
nearestTurnpikeInterchange
Indicates that one location is the closest turnpike interchange to another specified location.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 28, 2026, 2:47 p.m.