Triple
T21835756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Okmok |
E539114
|
entity |
| Predicate | hasCalderaFloorElevation |
P45909
|
FINISHED |
| Object | approximately 400 meters above 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: approximately 400 meters above sea level | Statement: [Mount Okmok, hasCalderaFloorElevation, approximately 400 meters above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalderaFloorElevation Context triple: [Mount Okmok, hasCalderaFloorElevation, approximately 400 meters above sea level]
-
A.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
-
B.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
C.
damCrestElevation
Indicates the height of the top (crest) of a dam above a specified reference level, typically sea level.
-
D.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
-
E.
elevationApproxMeters
chosen
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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a7c368819094e0c4548be30798 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.