Triple
T19782470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atal Tunnel (Rohtang) |
E475171
|
entity |
| Predicate | distanceReduction |
P55592
|
FINISHED |
| Object | about 46 kilometres |
—
|
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 46 kilometres | Statement: [Atal Tunnel (Rohtang), distanceReduction, about 46 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceReduction Context triple: [Atal Tunnel (Rohtang), distanceReduction, about 46 kilometres]
-
A.
significantlyShortensRouteBetween
Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
distanceChange
chosen
Indicates a change in the spatial distance between two entities over time.
-
D.
targetReduction
Indicates a relationship where one entity is intended or expected to decrease, diminish, or lessen another entity by a specified amount or proportion.
-
E.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
- 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_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. |
Created at: April 10, 2026, 1:49 p.m.