Triple

T37460797
Position Surface form Disambiguated ID Type / Status
Subject Spectral Knight E930910 entity
Predicate summoningSickness P191930 FINISHED
Object affected 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: affected | Statement: [Spectral Knight, summoningSickness, affected]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: summoningSickness
Context triple: [Spectral Knight, summoningSickness, affected]
  • A. summonedMinionText
    Indicates that one entity has called forth or created another entity to serve as its minion.
  • B. summonedMinionKeyword
    Indicates that one entity has been brought into play or created as a subordinate or controlled minion by another entity.
  • C. hasManaCost
    Indicates that an entity (such as a spell or ability) requires a specified amount of mana to be used or activated.
  • D. rewardMinionMechanic
    Indicates that an entity grants a benefit or bonus to a minion as part of a game or system mechanic.
  • E. summonedMinionHealth
    Indicates the health value of a minion that has been summoned by another entity.
  • F. None of above. chosen

Provenance (4 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_69fcef654d588190b29ecc76678d1aa0 completed May 7, 2026, 8 p.m.
PD Predicate disambiguation batch_69fcecdb97f48190b382b7d13be92dc0 completed May 7, 2026, 7:49 p.m.
PDg Predicate description generation batch_69fcef636dfc819085cf91323f2e4edd completed May 7, 2026, 8 p.m.
Created at: May 3, 2026, 4:17 p.m.