Triple
T36960648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomblade |
E914297
|
entity |
| Predicate | executionAnimationFeature |
P96809
|
FINISHED |
| Object | contextual kill animations |
—
|
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: contextual kill animations | Statement: [Doomblade, executionAnimationFeature, contextual kill animations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionAnimationFeature Context triple: [Doomblade, executionAnimationFeature, contextual kill animations]
-
A.
featuresAnimation
chosen
Indicates that something includes or prominently presents an animation as part of its content or functionality.
-
B.
executionTrigger
Indicates that one event, condition, or action initiates or causes the execution of another process or operation.
-
C.
executionDescription
Indicates the specific manner, details, or narrative of how an execution (of a process, action, or event) is or was carried out.
-
D.
movementFeatured
Indicates that a particular movement, action, or motion is prominently highlighted or given special emphasis within a broader context or sequence.
-
E.
stageActionFeature
Indicates that a particular action is performed or occurs during a specific stage or phase of a process or workflow.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.