Triple
T16814359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 95A |
E408701
|
entity |
| Predicate | stateHighwayNetwork |
P88251
|
FINISHED |
| Object | Nevada state highway system |
—
|
LITERAL FINISHED |
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 highway system | Statement: [U.S. Route 95A, stateHighwayNetwork, Nevada state highway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayNetwork Context triple: [U.S. Route 95A, stateHighwayNetwork, Nevada state highway system]
-
A.
nationalHighwayNetworkState
Indicates that a state is part of, or associated with, the national highway network.
-
B.
nationalHighwayConnectivity
Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
-
C.
stateHighwayDesignationIn
chosen
Indicates that a roadway has been designated as a state highway within a specified jurisdiction or region.
-
D.
highwayNumberingSystem
Indicates a system that assigns and organizes numerical designations to highways within a road network.
-
E.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e01fb8819081cf2c08f29448da |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.