Triple
T299150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deccan Traps volcanism |
E6159
|
entity |
| Predicate | debatedAsCauseOf |
P10554
|
FINISHED |
| Object | K–Pg boundary environmental crisis |
—
|
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: K–Pg boundary environmental crisis | Statement: [Deccan Traps volcanism, debatedAsCauseOf, K–Pg boundary environmental crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debatedAsCauseOf Context triple: [Deccan Traps volcanism, debatedAsCauseOf, K–Pg boundary environmental crisis]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
C.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9398df08190af40063a2de7a1d0 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.