Triple
T37554396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgement Legplates |
E933659
|
entity |
| Predicate | transmogUsage |
P200971
|
FINISHED |
| Object | popular paladin transmog choice |
—
|
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: popular paladin transmog choice | Statement: [Judgement Legplates, transmogUsage, popular paladin transmog choice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmogUsage Context triple: [Judgement Legplates, transmogUsage, popular paladin transmog choice]
-
A.
cannotBeTransmogrified
Indicates that the subject is not capable of being transformed or altered into a different form or state.
-
B.
isDisenchantable
Indicates that an item or object can be broken down or nullified using a disenchanting process.
-
C.
legendaryTransmission
Indicates the passing down or spread of stories, knowledge, or status through legend or myth rather than direct evidence or ordinary communication.
-
D.
isReforgingOf
Indicates that one object is the result of being remade, reshaped, or reconstructed from another pre-existing object.
-
E.
canBeEnchantedWith
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.