Triple
T10379012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 120 |
E244582
|
entity |
| Predicate | mountainPassElevation |
P79445
|
FINISHED |
| Object | Tioga Pass over 9,900 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: Tioga Pass over 9,900 feet | Statement: [State Route 120, mountainPassElevation, Tioga Pass over 9,900 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainPassElevation Context triple: [State Route 120, mountainPassElevation, Tioga Pass over 9,900 feet]
-
A.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
B.
eastSummitElevation
Indicates the elevation of the summit located on the eastern side of a geographic feature or area.
-
C.
highestPassApproxElevation
chosen
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
D.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
E.
trailheadElevation
Indicates the elevation at which a trail begins, typically measured at its starting point or trailhead.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98fead88190ace49f34b8a27c25 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:03 p.m.