Triple
T29610367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel Cliff |
E754699
|
entity |
| Predicate | locationRelativeToMountain |
P44470
|
FINISHED |
| Object | south side 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: south side of Mount Hood | Statement: [Steel Cliff, locationRelativeToMountain, south side of Mount Hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToMountain Context triple: [Steel Cliff, locationRelativeToMountain, south side of Mount Hood]
-
A.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
B.
locatedInMountain
Indicates that something is situated within, on, or as part of a mountain.
-
C.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
D.
relativeLocationToDenali
Indicates the spatial position or orientation of something in relation to Denali’s location.
-
E.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: April 28, 2026, 6:28 p.m.