Triple
T30192395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamunotri region |
E767526
|
entity |
| Predicate | distanceFromRishikesh |
P112531
|
FINISHED |
| Object | about 200–230 kilometres by road |
—
|
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 200–230 kilometres by road | Statement: [Yamunotri region, distanceFromRishikesh, about 200–230 kilometres by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRishikesh Context triple: [Yamunotri region, distanceFromRishikesh, about 200–230 kilometres by road]
-
A.
distanceFromRishikesh_km
chosen
Indicates the physical distance, measured in kilometers, between a given place and Rishikesh.
-
B.
distanceToHaridwar
Indicates the spatial distance between a given entity’s location and the location of Haridwar.
-
C.
distanceFromKullu
Indicates the spatial distance measured from the reference location Kullu to another place or entity.
-
D.
distanceToDehradun
Indicates the spatial distance between an entity’s location and the city of Dehradun.
-
E.
distanceFromKasol
Indicates the spatial distance measured from the reference location Kasol to another place or entity.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: April 29, 2026, 7:29 p.m.