Triple
T8728421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rae Lakes Loop |
E207187
|
entity |
| Predicate | elevationGainFeet |
P30489
|
FINISHED |
| Object | over 6000 |
—
|
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 6000 | Statement: [Rae Lakes Loop, elevationGainFeet, over 6000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationGainFeet Context triple: [Rae Lakes Loop, elevationGainFeet, over 6000]
-
A.
totalAscent
chosen
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
B.
elevationFeetApproximate
Indicates the approximate elevation of an entity above sea level, measured in feet.
-
C.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
D.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
- 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.