Triple
T38583888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowmoon Valley |
E932302
|
entity |
| Predicate | controllingNPC |
P199217
|
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: [Shadowmoon Valley, controllingNPC, Illidan Stormrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllingNPC Context triple: [Shadowmoon Valley, controllingNPC, Illidan Stormrage]
-
A.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
B.
controllingPlayer
Indicates which player currently has control or authority over a given game element, object, or situation.
-
C.
controlledByInGame
chosen
Indicates that one in-game entity has control or command over another within the context of the game.
-
D.
hasCharacterControl
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
-
E.
manipulatesProtagonistDuring
Indicates that one entity exerts deceptive or controlling influence over the protagonist during a specified time or event.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:32 p.m.