Triple
T37459527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vol'jin |
E930882
|
entity |
| Predicate | successorAsWarchief |
P202709
|
FINISHED |
| Object | Sylvanas Windrunner |
—
|
NE NERFINISHED |
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: Sylvanas Windrunner | Statement: [Vol'jin, successorAsWarchief, Sylvanas Windrunner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsWarchief Context triple: [Vol'jin, successorAsWarchief, Sylvanas Windrunner]
-
A.
predecessorAsWarchief
Indicates that one entity previously held the position of warchief immediately before another entity.
-
B.
successorAsKingOfKings
Indicates that one entity directly follows another in holding the title or role of King of Kings.
-
C.
successorAsHighKing
Indicates that one entity becomes the next holder of the title or role of High King after another entity.
-
D.
successorAsKabaka
Indicates that one individual became the next Kabaka (king) following another in the royal succession.
-
E.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_6a00ae622d9c81909815b10ed11cddfe |
completed | May 10, 2026, 4:12 p.m. |
Created at: May 3, 2026, 4:17 p.m.