Triple
T28360359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aut–Banjar–Sainj road |
E718345
|
entity |
| Predicate | stateHighwayRegion |
P78333
|
FINISHED |
| Object | Himachal Pradesh road network |
—
|
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: Himachal Pradesh road network | Statement: [Aut–Banjar–Sainj road, stateHighwayRegion, Himachal Pradesh road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayRegion Context triple: [Aut–Banjar–Sainj road, stateHighwayRegion, Himachal Pradesh road network]
-
A.
nationalHighwayNetworkState
Indicates that a state is part of, or associated with, the national highway network.
-
B.
stateHighwayDesignationIn
Indicates that a roadway has been designated as a state highway within a specified jurisdiction or region.
-
C.
stateHighwayConnectivity
Indicates that there is a transportation connection or linkage between locations via a designated state highway.
-
D.
containsStateHighway
chosen
Indicates that a geographic area or region includes within its boundaries at least one designated state highway.
-
E.
partOfInterstateRegion
Indicates that one region is a constituent or included area within a larger interstate (multi-state) region.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 28, 2026, 12:51 a.m.