Triple
T3465953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrego Highway |
E73136
|
entity |
| Predicate | hasFormerRouteNumber |
P22310
|
FINISHED |
| Object | National Highway 54 |
—
|
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: National Highway 54 | Statement: [Warrego Highway, hasFormerRouteNumber, National Highway 54]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerRouteNumber Context triple: [Warrego Highway, hasFormerRouteNumber, National Highway 54]
-
A.
formerRouteNumber
chosen
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
B.
hasFormerStreetName
Indicates that an entity (such as a street or place) was previously known by a different street name.
-
C.
hasRouteNumberingScheme
Indicates that one entity uses or is assigned a particular system or scheme for numbering its routes.
-
D.
hasHistoricalRoute
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
E.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0f2d3881908a5fa871341564ed |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.