Triple
T26038142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal mountain glaciers of Alaska |
E647610
|
entity |
| Predicate | drainTo |
P4497
|
FINISHED |
| Object | Gulf of Alaska |
—
|
NE NERFINISHED |
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: Gulf of Alaska | Statement: [Coastal mountain glaciers of Alaska, drainTo, Gulf of Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainTo Context triple: [Coastal mountain glaciers of Alaska, drainTo, Gulf of Alaska]
-
A.
drainsPartOf
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
B.
drainedFor
Indicates that a resource, substance, or energy is removed from one entity for the benefit, use, or purpose of another entity.
-
C.
drainedIn
Indicates that a liquid, resource, or substance has flowed out from one entity and been discharged or emptied into another entity or location.
-
D.
drainedFrom
Indicates that a substance, resource, or liquid has been removed or emptied out from a particular source or container.
-
E.
drainsInto
chosen
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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061fd954819082000e723287e423 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:08 a.m.