Triple
T38643847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Azeroth |
E938667
|
entity |
| Predicate | cannotBeTransmogrified |
P193519
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heart of Azeroth, cannotBeTransmogrified, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeTransmogrified Context triple: [Heart of Azeroth, cannotBeTransmogrified, true]
-
A.
cannotBeEnchanted
Indicates that the subject is not capable of being affected or altered by enchantments or magical enhancements.
-
B.
cannotBeEnchantedWith
Indicates that an entity is not eligible or allowed to receive a specified enchantment.
-
C.
cannotBeCrafted
Indicates that the item or entity cannot be created or produced through any crafting process or recipe.
-
D.
cannotBeSmelted
Indicates that the subject cannot undergo smelting to be transformed or processed into another material or form.
-
E.
cannotBeRepaired
Indicates that an entity is in such a state of damage or defect that it cannot be restored to proper working condition.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 3, 2026, 4:32 p.m.