Triple
T32601363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porkchop Geyser |
E833382
|
entity |
| Predicate | causeOf1989Explosion |
P188118
|
FINISHED |
| Object | hydrothermal steam explosion |
—
|
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: hydrothermal steam explosion | Statement: [Porkchop Geyser, causeOf1989Explosion, hydrothermal steam explosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOf1989Explosion Context triple: [Porkchop Geyser, causeOf1989Explosion, hydrothermal steam explosion]
-
A.
causeOf1993Fire
Indicates the entity that was responsible for starting or bringing about the 1993 fire.
-
B.
consequenceOf1979Incident
Indicates that something occurs as a result of, or is causally linked to, the 1979 incident.
-
C.
firstMajorAccidentDescription
Indicates the textual description of an entity’s first major accident.
-
D.
causeOf1956Disaster
Indicates that the subject is the factor, event, or agent responsible for causing the specific disaster that occurred in 1956.
-
E.
hydrogenExplosionsOccurredIn
Indicates that one or more hydrogen explosions took place at the specified location or within the specified context.
- F. None of above. chosen
Provenance (4 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.