Triple
T37463283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tol'vir Warden |
E930971
|
entity |
| Predicate | minCostOfDrawnMinions |
P187948
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Tol'vir Warden, minCostOfDrawnMinions, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minCostOfDrawnMinions Context triple: [Tol'vir Warden, minCostOfDrawnMinions, 1]
-
A.
convertedManaCost
Indicates the total amount of mana required to cast a spell or card, normalized into a single numeric value regardless of the specific colors of mana involved.
-
B.
hasManaCost
Indicates that an entity (such as a spell or ability) requires a specified amount of mana to be used or activated.
-
C.
usesMinimumCopiesPerCard
Indicates that there is a constraint specifying the minimum number of copies of each card that must be used or included in a given context.
-
D.
damageCostNote
Indicates a descriptive note or explanation associated with the cost of damage, providing contextual or clarifying information about that damage-related expense.
-
E.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.