Triple
T26363626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 6 near Coaldale, Nevada |
E660272
|
entity |
| Predicate | nearbyJunctionWith |
P31669
|
FINISHED |
| Object | U.S. Route 95 |
—
|
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 95 | Statement: [U.S. Route 6 near Coaldale, Nevada, nearbyJunctionWith, U.S. Route 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyJunctionWith Context triple: [U.S. Route 6 near Coaldale, Nevada, nearbyJunctionWith, U.S. Route 95]
-
A.
nearJunctionOf
chosen
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
B.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
C.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
D.
nearestMajorRailwayJunction
Indicates the closest significant railway junction in terms of distance from a given location or entity.
-
E.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 26, 2026, 10:53 p.m.