Triple
T15287182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manikaran |
E365430
|
entity |
| Predicate | distanceFromKullu |
P117962
|
FINISHED |
| Object | about 35–40 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 35–40 kilometres | Statement: [Manikaran, distanceFromKullu, about 35–40 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromKullu Context triple: [Manikaran, distanceFromKullu, about 35–40 kilometres]
-
A.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
-
B.
distanceFromRishikesh_km
Indicates the physical distance, measured in kilometers, between a given place and Rishikesh.
-
C.
distanceToDharamshala
Indicates the spatial distance between a given entity and the location of Dharamshala.
-
D.
distanceFromKargil
Indicates the spatial distance between a given location and Kargil.
-
E.
distanceToSrinagar_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Srinagar.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e551bb0819094db097285443740 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:15 a.m.