Triple
T29623754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coleman Glacier approach |
E755072
|
entity |
| Predicate | typicalSideOfMountain |
P73665
|
FINISHED |
| Object | north side of Mount Baker |
—
|
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: north side of Mount Baker | Statement: [Coleman Glacier approach, typicalSideOfMountain, north side of Mount Baker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSideOfMountain Context triple: [Coleman Glacier approach, typicalSideOfMountain, north side of Mount Baker]
-
A.
sideOfMountain
chosen
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
B.
targetMountain
Indicates that an entity is the intended mountain destination or objective of another entity or action.
-
C.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
D.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
-
E.
mountainRangeOnOneSide
Indicates that a mountain range is located along or borders one side of a specified geographic feature or area.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
Created at: April 28, 2026, 6:36 p.m.