Triple
T27743462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Passes trek |
E701915
|
entity |
| Predicate | hasApproximateMaximumAltitude |
P109129
|
FINISHED |
| Object | over 5400 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: over 5400 metres | Statement: [Three Passes trek, hasApproximateMaximumAltitude, over 5400 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMaximumAltitude Context triple: [Three Passes trek, hasApproximateMaximumAltitude, over 5400 metres]
-
A.
highestAltitudeReachedBy
Indicates the maximum altitude that a given entity has ever attained.
-
B.
highestAltitudeReachedFeet
Indicates the maximum altitude, measured in feet, that an entity has reached.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
extendsToApproximateAltitude
chosen
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 4:13 p.m.