Triple
T26641851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzongri trek |
E668799
|
entity |
| Predicate | endAltitude |
P109129
|
FINISHED |
| Object | approximately 4000 metres |
—
|
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 4000 metres | Statement: [Dzongri trek, endAltitude, approximately 4000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endAltitude Context triple: [Dzongri trek, endAltitude, approximately 4000 metres]
-
A.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
-
B.
releaseAltitude
Indicates the altitude at which something is released, such as an object, payload, or substance.
-
C.
extendsToApproximateAltitude
chosen
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616320b9c8190b3a5792ffcfe3bc1 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:29 a.m.