Triple
T16686715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Assiniboine Provincial Park |
E405479
|
entity |
| Predicate | mainPeakElevation |
P99098
|
FINISHED |
| Object | 3618 metres (Mount Assiniboine) |
—
|
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: 3618 metres (Mount Assiniboine) | Statement: [Mount Assiniboine Provincial Park, mainPeakElevation, 3618 metres (Mount Assiniboine)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPeakElevation Context triple: [Mount Assiniboine Provincial Park, mainPeakElevation, 3618 metres (Mount Assiniboine)]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
C.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
D.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
E.
peakElevationMetres
chosen
Indicates the maximum height of an entity above sea level, measured in metres.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea63b7081908a055036172f9683 |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.