Triple
T25323857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessore Road |
E634955
|
entity |
| Predicate | roadNumberWithinNH |
P158389
|
FINISHED |
| Object | NH 12 |
—
|
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: NH 12 | Statement: [Jessore Road, roadNumberWithinNH, NH 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNumberWithinNH Context triple: [Jessore Road, roadNumberWithinNH, NH 12]
-
A.
UShighwayNumber
Indicates that a U.S. highway is identified by a specific route number.
-
B.
roadNumberType
Indicates the classification or type category assigned to a road’s identifying number (e.g., highway, route, local road).
-
C.
highwayNumberingSystem
Indicates a system that assigns and organizes numerical designations to highways within a road network.
-
D.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
E.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
- F. None of above. chosen
Provenance (4 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4969103f08190b227994b2051522c |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:29 p.m.