Triple
T37554178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulfuras, Hand of Ragnaros |
E933654
|
entity |
| Predicate | craftedUsing |
P21333
|
FINISHED |
| Object | Eye of Sulfuras |
—
|
NE NERFINISHED |
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: Eye of Sulfuras | Statement: [Sulfuras, Hand of Ragnaros, craftedUsing, Eye of Sulfuras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftedUsing Context triple: [Sulfuras, Hand of Ragnaros, craftedUsing, Eye of Sulfuras]
-
A.
craftedIn
Indicates that an object or work was created or produced at a particular place or within a specific location.
-
B.
craftable
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
C.
forgedWith
Indicates that something has been created, shaped, or formed through the use of a specified tool, material, method, or collaborative partner.
-
D.
madeWith
chosen
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
-
E.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
- 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_69f76eca55bc8190acf25741793d5dac |
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. |
Created at: May 3, 2026, 4:17 p.m.