Triple
T29622507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 240 historic alignment |
E755035
|
entity |
| Predicate | historicalRouteNumber |
P192753
|
FINISHED |
| Object | U.S. Route 240 |
—
|
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 240 | Statement: [U.S. Route 240 historic alignment, historicalRouteNumber, U.S. Route 240]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRouteNumber Context triple: [U.S. Route 240 historic alignment, historicalRouteNumber, U.S. Route 240]
-
A.
historicalRouteNumberOf
chosen
Indicates that one route number was previously used to designate the same route or segment as another, but is no longer its current official number.
-
B.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
C.
historicalRouteName
Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
-
D.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
E.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 28, 2026, 6:35 p.m.