Triple
T8559810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janki Chatti |
E202661
|
entity |
| Predicate | trekDistanceToYamunotri |
P83628
|
FINISHED |
| Object | about 5 to 6 kilometers |
—
|
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 5 to 6 kilometers | Statement: [Janki Chatti, trekDistanceToYamunotri, about 5 to 6 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekDistanceToYamunotri Context triple: [Janki Chatti, trekDistanceToYamunotri, about 5 to 6 kilometers]
-
A.
approxTrekDistanceFromGangotri
Indicates the approximate trekking distance measured from Gangotri to another location or point of interest.
-
B.
distanceToDharamshala
Indicates the spatial distance between a given entity and the location of Dharamshala.
-
C.
distanceToSrinagar_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Srinagar.
-
D.
distanceToHirakudDam_km
Indicates the physical distance, measured in kilometers, between a given location and the Hirakud Dam.
-
E.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.