Triple
T37463008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swamp King Dred |
E930964
|
entity |
| Predicate | attackTargetCondition |
P29885
|
FINISHED |
| Object | Enemy minions played by opponent |
—
|
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: Enemy minions played by opponent | Statement: [Swamp King Dred, attackTargetCondition, Enemy minions played by opponent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTargetCondition Context triple: [Swamp King Dred, attackTargetCondition, Enemy minions played by opponent]
-
A.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
B.
attackTargetType
Indicates the type or category of target that an attack is directed against.
-
C.
preAttackCondition
Indicates the circumstances or requirements that must be satisfied before an attack can be initiated.
-
D.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
E.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.