Triple
T23087733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highway 43 (old NH 78) |
E575656
|
entity |
| Predicate | previousRouteNumber |
P22310
|
FINISHED |
| Object | 78 |
—
|
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: 78 | Statement: [National Highway 43 (old NH 78), previousRouteNumber, 78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRouteNumber Context triple: [National Highway 43 (old NH 78), previousRouteNumber, 78]
-
A.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
B.
formerRouteNumber
chosen
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
C.
parentRouteNumber
Indicates that one route is the immediate higher-level or containing route from which another route is derived or subordinated.
-
D.
routeNumberPrecededBy
Indicates that one route number comes immediately before another route number in an ordered sequence.
-
E.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da7c54c81908b62d04ab1811b06 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.