Triple
T35830887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ner'zhul |
E1035792
|
entity |
| Predicate | voiceInHeadOf |
P184449
|
FINISHED |
| Object | Arthas Menethil |
E274198
|
NE 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: Arthas Menethil | Statement: [Ner'zhul, voiceInHeadOf, Arthas Menethil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceInHeadOf Context triple: [Ner'zhul, voiceInHeadOf, Arthas Menethil]
-
A.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
B.
mainSpeechBy
Indicates that a speech or primary address is delivered or given by a particular entity.
-
C.
soundDepartmentHead
Indicates that one entity serves as the head or chief person in charge of the sound department for the other entity (such as a film, show, or production).
-
D.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
E.
hasVoicing
Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
- F. None of above. chosen
Provenance (5 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d64825481909323a3599f552dd4 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:06 p.m.