Triple
T37459526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vol'jin |
E930882
|
entity |
| Predicate | predecessorAsWarchief |
P196571
|
FINISHED |
| Object | Garrosh Hellscream |
—
|
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: Garrosh Hellscream | Statement: [Vol'jin, predecessorAsWarchief, Garrosh Hellscream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsWarchief Context triple: [Vol'jin, predecessorAsWarchief, Garrosh Hellscream]
-
A.
predecessorAsCommander
Indicates that one entity previously held the role of commander before another entity in the same command position.
-
B.
predecessorAsSupremeRuler
Indicates that one entity previously held the position of supreme ruler immediately before another entity.
-
C.
predecessorAsLocalRuler
Indicates that one entity previously held the position of local ruler immediately before another entity in a given domain or territory.
-
D.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
-
E.
predecessorAsKing
Indicates that one entity previously held the position of king immediately before the other 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_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:17 p.m.