Triple
T7014011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hood Meadows |
E162654
|
entity |
| Predicate | sideOfMountain |
P73665
|
FINISHED |
| Object | southeast 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: southeast side of Mount Hood | Statement: [Mount Hood Meadows, sideOfMountain, southeast side of Mount Hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfMountain Context triple: [Mount Hood Meadows, sideOfMountain, southeast side of Mount Hood]
-
A.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
B.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
C.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
D.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
E.
adjacentMountain
Indicates that one mountain is directly next to or touching another mountain, with no significant separation between them.
- F. None of above. chosen
Provenance (4 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc59cbfc8190bba9ebd14143d43c |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8a4930081908f1ae1e6ca8a514c |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:34 p.m.