Triple
T22541117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Bane |
E557289
|
entity |
| Predicate | notableStoryEvent |
P148591
|
FINISHED |
| Object | attempted mass mind control via Bubble Shock! |
—
|
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: attempted mass mind control via Bubble Shock! | Statement: [the Bane, notableStoryEvent, attempted mass mind control via Bubble Shock!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStoryEvent Context triple: [the Bane, notableStoryEvent, attempted mass mind control via Bubble Shock!]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
-
C.
notableSubevent
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing event.
-
D.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
E.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3251808190a72b849157854d8d |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.