Triple
T37553501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion |
E933641
|
entity |
| Predicate | storyFocusCharacter |
P77485
|
FINISHED |
| Object | Illidan Stormrage |
—
|
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: Illidan Stormrage | Statement: [Legion, storyFocusCharacter, Illidan Stormrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyFocusCharacter Context triple: [Legion, storyFocusCharacter, Illidan Stormrage]
-
A.
characterInFocus
chosen
Indicates that a particular character is the primary subject or focal point within a given context, scene, or narrative segment.
-
B.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
C.
characterizationFocus
Indicates that the primary emphasis or concern of a characterization is directed toward a particular aspect, feature, or dimension of the subject.
-
D.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
E.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.