Triple
T37463009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swamp King Dred |
E930964
|
entity |
| Predicate | attackTriggerTiming |
P28440
|
FINISHED |
| Object | Immediately after opponent plays a minion |
—
|
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: Immediately after opponent plays a minion | Statement: [Swamp King Dred, attackTriggerTiming, Immediately after opponent plays a minion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTriggerTiming Context triple: [Swamp King Dred, attackTriggerTiming, Immediately after opponent plays a minion]
-
A.
attackOnYourTurn
Indicates that the action of attacking occurs during the subject’s own turn in the sequence of play or events.
-
B.
timeAfterAttack
Indicates that a specified time point occurs after an attack event has taken place.
-
C.
activationTime
chosen
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
attackFrequency
Indicates how often an attack occurs within a given period or context.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.