Triple
T37550964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Knight |
E933588
|
entity |
| Predicate | dpsSpecialization |
P187955
|
FINISHED |
| Object | Frost |
—
|
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: Frost | Statement: [Death Knight, dpsSpecialization, Frost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dpsSpecialization Context triple: [Death Knight, dpsSpecialization, Frost]
-
A.
mainCharacterSpecialization
Indicates the specific role, class, or area of expertise that the main character is focused on or specialized in.
-
B.
wowSpecialization
chosen
Indicates that one entity has a specific specialization, role, or class within the context of World of Warcraft in relation to another entity.
-
C.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
D.
unitSpecialization
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
E.
ritualSpecialization
Indicates a relationship where an entity is specifically focused on, trained in, or primarily responsible for performing a particular type of ritual or set of ritual practices.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.