Triple
T28817481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-OAE |
E727678
|
entity |
| Predicate | triggerHypothesis |
P58568
|
FINISHED |
| Object | massive volcanic CO2 emissions |
—
|
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: massive volcanic CO2 emissions | Statement: [T-OAE, triggerHypothesis, massive volcanic CO2 emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerHypothesis Context triple: [T-OAE, triggerHypothesis, massive volcanic CO2 emissions]
-
A.
trigger
chosen
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
B.
hypothesis
Indicates that a statement or proposition is tentatively assumed to be true and is subject to testing, evaluation, or proof.
-
C.
hasConsequenceHypothesis
Indicates that one situation, event, or statement is hypothesized to lead to or imply a particular consequence.
-
D.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
E.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 6:33 a.m.