Triple
T27383941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS Mount Hayes |
E691313
|
entity |
| Predicate | verticalDatum |
P157999
|
FINISHED |
| Object | mean sea level |
—
|
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: mean sea level | Statement: [USGS Mount Hayes, verticalDatum, mean sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticalDatum Context triple: [USGS Mount Hayes, verticalDatum, mean sea level]
-
A.
usesElevationDatum
chosen
Indicates that one entity bases its elevation measurements or height references on the elevation datum defined or provided by another entity.
-
B.
verticalLocation
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
-
C.
referenceSurface
Indicates that one entity serves as the surface or base relative to which another entity is positioned, aligned, or defined.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c89b7b88190a8b2af842f5f9cca |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:23 p.m.