Triple
T37458772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piloted Sky Golem |
E930864
|
entity |
| Predicate | summonCostRestriction |
P188231
|
FINISHED |
| Object | 4 mana |
—
|
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: 4 mana | Statement: [Piloted Sky Golem, summonCostRestriction, 4 mana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonCostRestriction Context triple: [Piloted Sky Golem, summonCostRestriction, 4 mana]
-
A.
summonedMinionCost
Indicates the resource cost required to summon a minion in the given context.
-
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.
hasManaCost
Indicates that an entity (such as a spell or ability) requires a specified amount of mana to be used or activated.
-
D.
manaCostRule
chosen
Indicates a rule or constraint governing how much mana must be paid or used to perform an action or activate an effect.
-
E.
deckbuildingConstraint
Indicates a rule or limitation that governs how components (such as cards or items) may be selected, combined, or included when constructing a deck or similar collection.
- 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.