Triple
T37457688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowreaper Anduin |
E930839
|
entity |
| Predicate | heroClassCharacter |
P100346
|
FINISHED |
| Object | Anduin Wrynn |
—
|
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: Anduin Wrynn | Statement: [Shadowreaper Anduin, heroClassCharacter, Anduin Wrynn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroClassCharacter Context triple: [Shadowreaper Anduin, heroClassCharacter, Anduin Wrynn]
-
A.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
exampleCharacter
Indicates that one entity is an illustrative or sample character associated with another entity, typically used for demonstration or example purposes.
-
C.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
D.
metCharacter
Indicates that one entity has encountered or been introduced to another entity at least once.
-
E.
studentCharacter
Indicates that one entity has the role or qualities of a student in relation to another entity, typically within an educational or learning context.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.