Triple
T26038164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal mountain glaciers of Alaska |
E647610
|
entity |
| Predicate | terminateIn |
P109534
|
FINISHED |
| Object | fjords |
—
|
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: fjords | Statement: [Coastal mountain glaciers of Alaska, terminateIn, fjords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminateIn Context triple: [Coastal mountain glaciers of Alaska, terminateIn, fjords]
-
A.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
-
B.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
-
C.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
D.
typicallyTerminatedIn
chosen
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
E.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
- 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 9:08 a.m.