Triple
T28386256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 80 |
E719026
|
entity |
| Predicate | establishedAsNumberedRoute |
P38215
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [US 80, establishedAsNumberedRoute, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsNumberedRoute Context triple: [US 80, establishedAsNumberedRoute, 1926]
-
A.
routeNumberSignedAs
Indicates that a route is officially signed or labeled with a particular route number on physical or digital signage.
-
B.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
C.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
D.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
E.
isNumberedHighway
chosen
Indicates that a roadway is officially designated and signed as a numbered highway within a road network.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 1:10 a.m.