Triple
T37461133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cho'gall |
E930918
|
entity |
| Predicate | classInWorldOfWarcraft |
P117259
|
FINISHED |
| Object | warlock-like raid boss |
—
|
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: warlock-like raid boss | Statement: [Cho'gall, classInWorldOfWarcraft, warlock-like raid boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classInWorldOfWarcraft Context triple: [Cho'gall, classInWorldOfWarcraft, warlock-like raid boss]
-
A.
relatedClassInWarcraft
Indicates that two entities are related through a class association within the Warcraft universe, such as sharing, corresponding to, or being mapped between specific Warcraft character classes.
-
B.
roleInWarcraft
chosen
Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
-
C.
mythicAlliance
Indicates a cooperative or strategic partnership formed between entities within a legendary, mythical, or supernatural context.
-
D.
crystalClass
Indicates the crystallographic symmetry class or system to which a crystal or mineral belongs.
-
E.
roleAtBlizzard
Indicates that an entity holds or held a specific role or position at the company Blizzard.
- 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_69f76ec1a1148190b0a961f188d621b0 |
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.