Triple
T5655678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mānoa Falls Trail |
E124611
|
entity |
| Predicate | hasApproximateElevationGain |
P55645
|
FINISHED |
| Object | about 600 feet |
—
|
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: about 600 feet | Statement: [Mānoa Falls Trail, hasApproximateElevationGain, about 600 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateElevationGain Context triple: [Mānoa Falls Trail, hasApproximateElevationGain, about 600 feet]
-
A.
hasApproxElevationFeet
chosen
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
B.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
C.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
D.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
E.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.