Triple
T8728402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rae Lakes Loop |
E207187
|
entity |
| Predicate | highestPointElevationFeet |
P19320
|
FINISHED |
| Object | approximately 11978 |
—
|
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 11978 | Statement: [Rae Lakes Loop, highestPointElevationFeet, approximately 11978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPointElevationFeet Context triple: [Rae Lakes Loop, highestPointElevationFeet, approximately 11978]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
D.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
E.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1890e0819088b271db51faa738 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.