Triple
T25177777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Triple Divide Peak |
E630493
|
entity |
| Predicate | usesElevationDatum |
P157999
|
FINISHED |
| Object | USGS vertical datum |
—
|
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: USGS vertical datum | Statement: [USGS Triple Divide Peak, usesElevationDatum, USGS vertical datum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElevationDatum Context triple: [USGS Triple Divide Peak, usesElevationDatum, USGS vertical datum]
-
A.
usesMetricElevation
Indicates that an entity’s elevation is expressed using metric units (such as meters) rather than non-metric units.
-
B.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
C.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
D.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
E.
elevationAboveSeaLevelUnit
Indicates the unit of measurement used to express an entity’s elevation above sea level.
- F. None of above. chosen
Provenance (4 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc1ddd0819089722f45adc50d84 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:35 p.m.