Triple
T24019256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everest Base Camp (South) |
E594769
|
entity |
| Predicate | trekDistanceFromLukla |
P154884
|
FINISHED |
| Object | approximately 65 kilometres one way |
—
|
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 65 kilometres one way | Statement: [Everest Base Camp (South), trekDistanceFromLukla, approximately 65 kilometres one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekDistanceFromLukla Context triple: [Everest Base Camp (South), trekDistanceFromLukla, approximately 65 kilometres one way]
-
A.
distanceToThimphu
Indicates the measured spatial distance between a given entity’s location and the city of Thimphu.
-
B.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
-
C.
distanceToThimphuByRoad
Indicates the road travel distance required to go from a given place to Thimphu.
-
D.
distanceFromKullu
Indicates the spatial distance measured from the reference location Kullu to another place or entity.
-
E.
distanceToNepalgunj_km
Indicates the physical distance, measured in kilometers, between a given location and Nepalgunj.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a7b5848190849e7a0f035465b3 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:42 p.m.