Triple
T32601364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porkchop Geyser |
E833382
|
entity |
| Predicate | effectOf1989Explosion |
P70979
|
FINISHED |
| Object | crater enlargement |
—
|
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: crater enlargement | Statement: [Porkchop Geyser, effectOf1989Explosion, crater enlargement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOf1989Explosion Context triple: [Porkchop Geyser, effectOf1989Explosion, crater enlargement]
-
A.
causeOf1989Explosion
Indicates that the subject is the cause or origin of an explosion that occurred in 1989.
-
B.
consequenceOfExplosion
chosen
Indicates that something occurs as a direct result or outcome of an explosion.
-
C.
safetyChangesAfterExplosion
Indicates that the safety status or conditions of an entity are altered as a result of an explosion.
-
D.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
E.
consequenceOf1979Incident
Indicates that something occurs as a result of, or is causally linked to, the 1979 incident.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:05 a.m.