Triple
T26081199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada State Route 169 |
E657846
|
entity |
| Predicate | hasRouteNumberFollowedBy |
P127887
|
FINISHED |
| Object | Nevada State Route 170 |
—
|
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: Nevada State Route 170 | Statement: [Nevada State Route 169, hasRouteNumberFollowedBy, Nevada State Route 170]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNumberFollowedBy Context triple: [Nevada State Route 169, hasRouteNumberFollowedBy, Nevada State Route 170]
-
A.
routeNumberFollowedBy
chosen
Indicates that one route number directly succeeds another in a defined ordering or sequence.
-
B.
hasRoadNumberAfter
Indicates that one road’s designated number comes later in a defined sequence or ordering than another road’s number.
-
C.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
D.
routeNumberPrecededBy
Indicates that one route number comes immediately before another route number in an ordered sequence.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 7:38 p.m.