Triple
T37540857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyra the Sunshard |
E933320
|
entity |
| Predicate | disenchantValue |
P187935
|
FINISHED |
| Object | 400 Arcane Dust (normal) in standard Hearthstone economy |
—
|
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: 400 Arcane Dust (normal) in standard Hearthstone economy | Statement: [Lyra the Sunshard, disenchantValue, 400 Arcane Dust (normal) in standard Hearthstone economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disenchantValue Context triple: [Lyra the Sunshard, disenchantValue, 400 Arcane Dust (normal) in standard Hearthstone economy]
-
A.
disenchantValueEpic
Indicates the value or outcome obtained when an epic-quality item is disenchanted.
-
B.
dustValueToDisenchant
chosen
Indicates the amount of dust received when an item is disenchanted.
-
C.
isDisenchantable
Indicates that an item or object can be broken down or nullified using a disenchanting process.
-
D.
enchantable
Indicates that an entity is capable of being affected by or imbued with magical enchantments.
-
E.
enchantment
Indicates that one entity has placed a magical or supernatural influence on another, altering its state, behavior, or properties.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.