Triple
T27743461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Passes trek |
E701915
|
entity |
| Predicate | hasHighestPassElevation |
P79445
|
FINISHED |
| Object | approximately 5535 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 5535 metres | Statement: [Three Passes trek, hasHighestPassElevation, approximately 5535 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPassElevation Context triple: [Three Passes trek, hasHighestPassElevation, approximately 5535 metres]
-
A.
highestPassApproxElevation
chosen
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
hasHighestElevationsOf
Indicates that one entity possesses the greatest elevation values (e.g., altitudes or heights) compared to another entity or set of entities.
-
D.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
E.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
- 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 4:13 p.m.