Triple
T15403494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coleman Glacier |
E368386
|
entity |
| Predicate | drainsFlankOf |
P84938
|
FINISHED |
| Object | northwest flank 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: northwest flank of Mount Baker | Statement: [Coleman Glacier, drainsFlankOf, northwest flank of Mount Baker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsFlankOf Context triple: [Coleman Glacier, drainsFlankOf, northwest flank of Mount Baker]
-
A.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
-
B.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
C.
drainsPartOf
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
D.
drainageBetween
Indicates that one area or feature serves as a drainage path or channel between two other areas or features, allowing water or runoff to flow from one to the other.
-
E.
flowsDownFlankOf
chosen
Indicates that one entity moves or travels downward along the side or slope of another entity.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ea0ac8190a5c68b1951ad3db1 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.