Triple
T19782467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atal Tunnel (Rohtang) |
E475171
|
entity |
| Predicate | elevationNorthPortal |
P137307
|
FINISHED |
| Object | about 3071 metres |
—
|
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: about 3071 metres | Statement: [Atal Tunnel (Rohtang), elevationNorthPortal, about 3071 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationNorthPortal Context triple: [Atal Tunnel (Rohtang), elevationNorthPortal, about 3071 metres]
-
A.
elevationAtEastPortal
Indicates the elevation value measured at the eastern portal of a structure or feature.
-
B.
elevationAtWestPortal
Indicates the elevation value measured at the western entrance or portal of a structure, route, or geographic feature.
-
C.
summitElevationNorth
Indicates the elevation of the summit located to the north relative to a given reference point or feature.
-
D.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
E.
elevationConnection
Indicates a relationship where one entity is linked to another through a change or difference in elevation, such as a vertical or sloped connection between their heights or levels.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653852e848190b8971981a164e8f9 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.