Triple
T38593024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Blossom |
E932496
|
entity |
| Predicate | canBeInterruptedBy |
P93399
|
FINISHED |
| Object | stuns |
—
|
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: stuns | Statement: [Death Blossom, canBeInterruptedBy, stuns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeInterruptedBy Context triple: [Death Blossom, canBeInterruptedBy, stuns]
-
A.
wasInterruptedBy
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
B.
supportsInterrupt
Indicates that one entity is capable of handling or accommodating an interruption initiated by another entity.
-
C.
canBeIntervenedBy
Indicates that an entity is susceptible to or eligible for intervention by another entity or agent.
-
D.
canBeStopped
Indicates that an ongoing process, action, or state is capable of being halted or brought to an end.
-
E.
canBeDisturbedBy
chosen
Indicates that an entity is susceptible to being interrupted, bothered, or otherwise negatively affected by another entity or factor.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:32 p.m.