Triple
T8275500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signal Mountain |
E193536
|
entity |
| Predicate | relativeHeightAboveJacksonLake |
P37154
|
FINISHED |
| Object | about 800 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 800 feet | Statement: [Signal Mountain, relativeHeightAboveJacksonLake, about 800 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeightAboveJacksonLake Context triple: [Signal Mountain, relativeHeightAboveJacksonLake, about 800 feet]
-
A.
elevationAboveLake
chosen
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
D.
deckHeightAboveValley
Indicates that the height of a deck is measured relative to, and positioned above, the elevation of a valley.
-
E.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798d69508190b581ad8a38730175 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.