Triple
T37872982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Klaxxi |
E944649
|
entity |
| Predicate | raidEncounterRole |
P188181
|
FINISHED |
| Object | boss faction in Siege of Orgrimmar |
—
|
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: boss faction in Siege of Orgrimmar | Statement: [The Klaxxi, raidEncounterRole, boss faction in Siege of Orgrimmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidEncounterRole Context triple: [The Klaxxi, raidEncounterRole, boss faction in Siege of Orgrimmar]
-
A.
raidRole
chosen
Indicates a role or function that an entity holds or performs within the context of a raid or coordinated attack.
-
B.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
C.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
-
D.
raidID
Indicates a unique identifier that associates entities with a specific raid event or operation.
-
E.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.