Triple
T12307717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hive (MCU) |
E293395
|
entity |
| Predicate | mannerOfDefeat |
P44055
|
FINISHED |
| Object | killed in space by nuclear warhead |
—
|
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: killed in space by nuclear warhead | Statement: [Hive (MCU), mannerOfDefeat, killed in space by nuclear warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannerOfDefeat Context triple: [Hive (MCU), mannerOfDefeat, killed in space by nuclear warhead]
-
A.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
B.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
C.
afterDefeat
Indicates that one event, state, or action occurs subsequent to and as a consequence of a defeat of some party or entity.
-
D.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
E.
methodOfDefeat
chosen
Indicates the specific way or technique by which one entity defeats or overcomes another.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.