Triple
T359637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Range foothills |
E7819
|
entity |
| Predicate | hasRelativeElevation |
P221
|
FINISHED |
| Object | higher than surrounding lowland valleys |
—
|
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: higher than surrounding lowland valleys | Statement: [Cascade Range foothills, hasRelativeElevation, higher than surrounding lowland valleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeElevation Context triple: [Cascade Range foothills, hasRelativeElevation, higher than surrounding lowland valleys]
-
A.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
B.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
elevationChange
Indicates a change in vertical position or altitude between two points or states.
-
D.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
E.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb248608190b060553219616043 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.