Triple
T15431025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohtang Pass |
E369638
|
entity |
| Predicate | AtalTunnelPurpose |
P118747
|
FINISHED |
| Object | to provide all-weather connectivity between Manali and Lahaul |
—
|
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: to provide all-weather connectivity between Manali and Lahaul | Statement: [Rohtang Pass, AtalTunnelPurpose, to provide all-weather connectivity between Manali and Lahaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AtalTunnelPurpose Context triple: [Rohtang Pass, AtalTunnelPurpose, to provide all-weather connectivity between Manali and Lahaul]
-
A.
tunnelDugBy
Indicates that a tunnel was created or excavated by a particular agent or entity.
-
B.
tollPurpose
Indicates that a toll is imposed for a specific purpose, such as funding, maintenance, or use of a particular facility or service.
-
C.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
D.
hasSummitTunnel
Indicates that a summit or peak contains or is traversed by a tunnel.
-
E.
numberOfMajorTunnels
Indicates the count of primary or significant tunnels associated with an entity.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ed8ea888190bff8dc14859cca31 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.