Triple
T29083105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annihilation: Conquest |
E734030
|
entity |
| Predicate | featuresInvasionOf |
P113615
|
FINISHED |
| Object | Kree Empire |
—
|
NE NERFINISHED |
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: Kree Empire | Statement: [Annihilation: Conquest, featuresInvasionOf, Kree Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInvasionOf Context triple: [Annihilation: Conquest, featuresInvasionOf, Kree Empire]
-
A.
invasionAddressed
Indicates that an invasion event has been responded to or dealt with through some form of action, intervention, or resolution.
-
B.
effectOnInvasion
Indicates the influence or impact that one factor has on the occurrence, success, or intensity of an invasion.
-
C.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
D.
invasionCodename
Indicates the codename assigned to a specific military invasion operation.
-
E.
invadesFrom
Indicates that one entity initiates an invasion or aggressive incursion into another entity starting from a specified origin or source location.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: April 28, 2026, 10:57 a.m.