Triple
T37463778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rush (Hearthstone keyword) |
E930983
|
entity |
| Predicate | attackTargetLimitationOnSummon |
P190404
|
FINISHED |
| Object | Minions only |
—
|
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: Minions only | Statement: [Rush (Hearthstone keyword), attackTargetLimitationOnSummon, Minions only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTargetLimitationOnSummon Context triple: [Rush (Hearthstone keyword), attackTargetLimitationOnSummon, Minions only]
-
A.
summonCount
Indicates the number of times an entity has been summoned or caused to appear.
-
B.
canBeSummonedByPlayer
Indicates that the entity is capable of being brought into the game world or into action through a summoning action performed by a player.
-
C.
conditionToSummon
Indicates that a specific condition or set of conditions must be met in order for an entity to be summoned.
-
D.
canSummonToken
Indicates that an entity has the ability to create or bring forth a specific token into play or existence.
-
E.
canSummonDuplicateTotem
Indicates that an entity has the ability to summon an additional instance of an existing totem simultaneously.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:17 p.m.