Triple
T37507639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.1 Chains of Domination |
E932137
|
entity |
| Predicate | dungeonType |
P188692
|
FINISHED |
| Object | mega-dungeon |
—
|
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: mega-dungeon | Statement: [World of Warcraft patch 9.1 Chains of Domination, dungeonType, mega-dungeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dungeonType Context triple: [World of Warcraft patch 9.1 Chains of Domination, dungeonType, mega-dungeon]
-
A.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
B.
majorDungeonFeature
Indicates that something serves as a primary or defining structural or thematic element of a dungeon.
-
C.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
D.
caveType
Indicates the specific classification or kind of cave associated with an entity.
-
E.
dungeonCountAtLaunch
Indicates the number of dungeons available when the game or content is first released.
- F. None of above. chosen
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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.