Triple
T37459668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimiron's Head |
E930885
|
entity |
| Predicate | destroyEffect |
P100792
|
FINISHED |
| Object | destroys all your Mechs when its condition is met |
—
|
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: destroys all your Mechs when its condition is met | Statement: [Mimiron's Head, destroyEffect, destroys all your Mechs when its condition is met]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyEffect Context triple: [Mimiron's Head, destroyEffect, destroys all your Mechs when its condition is met]
-
A.
damageEffect
chosen
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
B.
terminateEffect
Indicates that an ongoing effect, condition, or process is brought to an end or cancelled.
-
C.
failureEffect
Indicates the resulting condition, consequence, or outcome that occurs when a failure happens.
-
D.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
E.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.