Triple
T23872704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merzbacher Lake |
E592769
|
entity |
| Predicate | outburstCause |
P150642
|
FINISHED |
| Object | collapse of ice dam |
—
|
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: collapse of ice dam | Statement: [Merzbacher Lake, outburstCause, collapse of ice dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outburstCause Context triple: [Merzbacher Lake, outburstCause, collapse of ice dam]
-
A.
outburstType
Indicates the specific kind or category of outburst that occurred in a given situation.
-
B.
outburst
Indicates a sudden, intense expression of emotion or reaction directed from one entity toward another or into a situation.
-
C.
possibleOriginOfOutburst
Indicates that one entity is a potential cause or source of another entity’s outburst or sudden reaction.
-
D.
outburstAmplitude
Indicates the magnitude or intensity level of an outburst event relative to a baseline or typical state.
-
E.
outburstEnergySource
chosen
Indicates that one entity serves as the source or cause of the energy released in an outburst associated with 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.