Triple
T7956557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliot Glacier |
E184752
|
entity |
| Predicate | locatedOnSlope |
P56549
|
FINISHED |
| Object | northeastern slope of Mount Hood |
—
|
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: northeastern slope of Mount Hood | Statement: [Eliot Glacier, locatedOnSlope, northeastern slope of Mount Hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSlope Context triple: [Eliot Glacier, locatedOnSlope, northeastern slope of Mount Hood]
-
A.
locatedOnTerrain
chosen
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
blowsDownSlopeOf
Indicates that something (typically wind or air) moves or exerts force downward along the incline or gradient of a slope relative to another entity.
-
C.
locatedOnEasternSlopeOf
Indicates that one entity is situated on the eastern slope or side of another geographic feature or elevation.
-
D.
hasSettlementOnSlopes
Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
-
E.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b7d36c081908cc8760a0dbf6001 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.