Triple
T15446649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cucamonga Peak |
E370039
|
entity |
| Predicate | typicalElevationGain |
P94224
|
FINISHED |
| Object | ~4000 ft via Icehouse Canyon |
—
|
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: ~4000 ft via Icehouse Canyon | Statement: [Cucamonga Peak, typicalElevationGain, ~4000 ft via Icehouse Canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalElevationGain Context triple: [Cucamonga Peak, typicalElevationGain, ~4000 ft via Icehouse Canyon]
-
A.
hasApproxElevationGainFt
chosen
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
B.
typicalStartElevation
Indicates the usual or characteristic elevation at which something (such as a route, feature, or activity) typically begins.
-
C.
elevationGainFunction
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
D.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
E.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef767b4819099f2c0919a158321 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.