Triple
T26641849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzongri trek |
E668799
|
entity |
| Predicate | startingAltitude |
P21269
|
FINISHED |
| Object | approximately 1780 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 1780 metres | Statement: [Dzongri trek, startingAltitude, approximately 1780 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingAltitude Context triple: [Dzongri trek, startingAltitude, approximately 1780 metres]
-
A.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
B.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
-
C.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
extendsToApproximateAltitude
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
E.
releaseAltitude
Indicates the altitude at which something is released, such as an object, payload, or substance.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 2:29 a.m.