Triple
T22020537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major William Cage |
E543832
|
entity |
| Predicate | gainsPowerFrom |
P82640
|
FINISHED |
| Object | Mimic alpha blood |
—
|
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: Mimic alpha blood | Statement: [Major William Cage, gainsPowerFrom, Mimic alpha blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainsPowerFrom Context triple: [Major William Cage, gainsPowerFrom, Mimic alpha blood]
-
A.
gainedPowerAfter
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving another entity.
-
B.
enhancesPowersOf
chosen
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
C.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
D.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
E.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c6b5fc8190bc49ddb058f28a44 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.