Triple
T16565289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulandshahr |
E402443
|
entity |
| Predicate | majorHighwayConnection |
P385
|
FINISHED |
| Object | National Highway 34 |
—
|
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 34 | Statement: [Bulandshahr, majorHighwayConnection, National Highway 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHighwayConnection Context triple: [Bulandshahr, majorHighwayConnection, National Highway 34]
-
A.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
nationalHighwayConnectivity
Indicates the extent to which locations are linked by a network of national highways enabling direct or efficient road travel between them.
-
C.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
E.
expresswayInterchange
Indicates a road connection where an expressway intersects with another road or expressway, allowing vehicles to transfer between them.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e357711ea481909468147375051bb4 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.