Triple
T29603318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trail of Ten Falls |
E754508
|
entity |
| Predicate | elevationGainInFeet |
P116668
|
FINISHED |
| Object | 800 |
—
|
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: 800 | Statement: [Trail of Ten Falls, elevationGainInFeet, 800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationGainInFeet Context triple: [Trail of Ten Falls, elevationGainInFeet, 800]
-
A.
hasApproxElevationGainFt
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
B.
elevationGainFunction
chosen
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
C.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
D.
elevationFeetApproximate
Indicates the approximate elevation of an entity above sea level, measured in feet.
-
E.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 6:23 p.m.