Triple
T37553514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion |
E933641
|
entity |
| Predicate | loreEvent |
P174417
|
FINISHED |
| Object | third major Burning Legion invasion of Azeroth |
—
|
LITERAL 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: third major Burning Legion invasion of Azeroth | Statement: [Legion, loreEvent, third major Burning Legion invasion of Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreEvent Context triple: [Legion, loreEvent, third major Burning Legion invasion of Azeroth]
-
A.
expeditionEvent
Indicates an event or occurrence that takes place as part of, or in direct connection with, an expedition.
-
B.
storySettingEvent
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
C.
storylineEvent
chosen
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
D.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
E.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.