Triple
T19608375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palampur |
E470664
|
entity |
| Predicate | distanceFromDharamshala_km |
P54980
|
FINISHED |
| Object | approximately 35 |
—
|
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: approximately 35 | Statement: [Palampur, distanceFromDharamshala_km, approximately 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDharamshala_km Context triple: [Palampur, distanceFromDharamshala_km, approximately 35]
-
A.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
-
B.
distanceToDharamshala
chosen
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.
distanceFromChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
-
E.
distanceToChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Chandigarh.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c964fc8190bd1cb60f4b233eaa |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.