Triple
T22548878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterpocket Fold |
E557503
|
entity |
| Predicate | maximumVerticalRelief |
P19604
|
FINISHED |
| Object | up to about 7,000 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: up to about 7,000 feet | Statement: [Waterpocket Fold, maximumVerticalRelief, up to about 7,000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumVerticalRelief Context triple: [Waterpocket Fold, maximumVerticalRelief, up to about 7,000 feet]
-
A.
maximumVolcanicRelief
Indicates the greatest vertical difference in elevation within a volcanic landform or volcanic region.
-
B.
hasRelativeRelief
chosen
Indicates a relationship where one entity is characterized by the degree of variation in elevation or relief relative to another reference entity or area.
-
C.
maximumPinnacleHeight
Indicates the greatest vertical height reached at the highest point (pinnacle) of an object, structure, or formation.
-
D.
maximumMoundHeight
Indicates the greatest allowable or observed height of a mound relative to a specified reference or context.
-
E.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f372df48190ae5dd461b1230bc7 |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.