Triple
T38022591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | statusInWoW |
P100147
|
FINISHED |
| Object | deceased |
—
|
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: deceased | Statement: [King Rastakhan, statusInWoW, deceased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInWoW Context triple: [King Rastakhan, statusInWoW, deceased]
-
A.
statusInDalaran
Indicates the standing, rank, or level of recognition an entity holds within the context of Dalaran.
-
B.
statusAfterBattleForAzeroth
chosen
Indicates the condition or state of an entity following the events of the Battle for Azeroth.
-
C.
statusInDiabloII
Indicates the role, condition, or classification an entity holds within the context of the game Diablo II.
-
D.
roleAtBlizzard
Indicates that an entity holds or held a specific role or position at the company Blizzard.
-
E.
roleInWarcraft
Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:20 p.m.