Triple
T37465298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamorphosis |
E931018
|
entity |
| Predicate | canTargetMinions |
P143292
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Metamorphosis, canTargetMinions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTargetMinions Context triple: [Metamorphosis, canTargetMinions, true]
-
A.
canAttackMinions
Indicates that an entity has the ability or permission to perform attacks specifically targeting minion-type entities.
-
B.
canDamageStealthedMinions
Indicates that an entity has the ability to inflict damage on minions that are currently in a stealthed or hidden state.
-
C.
summonedMinionAttack
Indicates that a minion, previously summoned by an entity, performs an attack action on a target.
-
D.
canTarget
chosen
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
E.
canRaiseUndeadMinions
Indicates the ability of an entity to animate and control undead creatures as subordinate minions.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.