Triple
T37507612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.1 Chains of Domination |
E932137
|
entity |
| Predicate | featuresRaid |
P80690
|
FINISHED |
| Object | Sanctum of Domination |
E273811
|
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: Sanctum of Domination | Statement: [World of Warcraft patch 9.1 Chains of Domination, featuresRaid, Sanctum of Domination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRaid Context triple: [World of Warcraft patch 9.1 Chains of Domination, featuresRaid, Sanctum of Domination]
-
A.
featuresRiseOf
Indicates that something includes or portrays the emergence or increasing prominence of someone or something.
-
B.
featuresCharacterRescue
Indicates that a work includes a scene or storyline in which one character rescues or saves another.
-
C.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
D.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
E.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4095350c3081909487ed31e9fadd9a |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.