Triple
T37507630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.1 Chains of Domination |
E932137
|
entity |
| Predicate | raidName |
P152630
|
FINISHED |
| Object | Sanctum of Domination |
—
|
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: Sanctum of Domination | Statement: [World of Warcraft patch 9.1 Chains of Domination, raidName, Sanctum of Domination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidName Context triple: [World of Warcraft patch 9.1 Chains of Domination, raidName, Sanctum of Domination]
-
A.
raidOperationName
chosen
Indicates the specific name or designation assigned to a particular raid operation.
-
B.
raid
Indicates a sudden, targeted attack or incursion by one party into another’s domain, typically to seize assets, gather information, or cause disruption.
-
C.
raidPosition
Indicates the spatial location or coordinates where a raid event takes place or is intended to occur.
-
D.
raidOrigin
Indicates the source location, group, or entity from which a raid is initiated or originates.
-
E.
raidSize
Indicates the number of participants or units involved in a single raid 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_69f76ec5268481909ea01c73aeeefd42 |
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.