Triple
T38644505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of Azshara |
E938680
|
entity |
| Predicate | includesRaidBoss |
P188713
|
FINISHED |
| Object | Queen Azshara |
E2232456
|
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: Queen Azshara | Statement: [Rise of Azshara, includesRaidBoss, Queen Azshara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRaidBoss Context triple: [Rise of Azshara, includesRaidBoss, Queen Azshara]
-
A.
raidBossIn
chosen
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
B.
requiresBossFight
Indicates that completing or progressing past a certain point necessitates defeating a designated boss character in combat.
-
C.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
D.
hasBossFights
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
E.
bossOrderInRaid
Indicates the sequence in which bosses are encountered or fought during a raid.
- F. None of above.
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f71f740819082c9c08a9693a4aa |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.