Triple
T51788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 71 |
E1016
|
entity |
| Predicate | highwayNumber |
P1864
|
FINISHED |
| Object | 71 |
—
|
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: 71 | Statement: [U.S. Route 71, highwayNumber, 71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highwayNumber Context triple: [U.S. Route 71, highwayNumber, 71]
-
A.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
B.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.