Triple
T359632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Range foothills |
E7819
|
entity |
| Predicate | topographicallyBetween |
P1262
|
FINISHED |
| Object | Cascade Range high peaks |
—
|
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: Cascade Range high peaks | Statement: [Cascade Range foothills, topographicallyBetween, Cascade Range high peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topographicallyBetween Context triple: [Cascade Range foothills, topographicallyBetween, Cascade Range high peaks]
-
A.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
topographicIsolation
Indicates the distance from a geographic feature to the nearest point of equal or greater elevation, expressing how isolated it is from higher terrain.
-
C.
topographicMap
Indicates a mapping relationship where a representation shows the physical terrain features and elevation contours of a geographic area.
-
D.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
E.
areaPeakApprox
Indicates an approximate measurement or estimation of the peak area associated with an entity or event.
- 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.