Triple
T27394560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erebus Glacier |
E691640
|
entity |
| Predicate | drainsFeature |
P51132
|
FINISHED |
| Object | Mount Erebus summit area |
—
|
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: Mount Erebus summit area | Statement: [Erebus Glacier, drainsFeature, Mount Erebus summit area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainsFeature Context triple: [Erebus Glacier, drainsFeature, Mount Erebus summit area]
-
A.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
-
B.
drainsNear
Indicates that one entity, typically a drainage feature or outlet, is located in close proximity to another relevant object or area.
-
C.
drainageAreaFeature
chosen
Indicates the geographic feature or area from which water drains into a particular water body or drainage system.
-
D.
drainsPartOf
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
E.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:27 p.m.