Triple
T38591610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scepter of the Shifting Sands |
E932465
|
entity |
| Predicate | requiresDungeon |
P202884
|
FINISHED |
| Object | Ruins of Ahn'Qiraj |
—
|
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: Ruins of Ahn'Qiraj | Statement: [Scepter of the Shifting Sands, requiresDungeon, Ruins of Ahn'Qiraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDungeon Context triple: [Scepter of the Shifting Sands, requiresDungeon, Ruins of Ahn'Qiraj]
-
A.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
B.
dungeonType
Indicates the specific category or kind of dungeon associated with an entity or location.
-
C.
requiresNPC
Indicates that one entity depends on the presence, involvement, or assistance of a non-player character (NPC) in order to occur, be valid, or be completed.
-
D.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
E.
majorDungeonFeature
Indicates that something serves as a primary or defining structural or thematic element of a dungeon.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
| PDg | Predicate description generation | batch_6a00ca5de6748190bc67a1fd9f3d0b3a |
completed | May 10, 2026, 6:11 p.m. |
Created at: May 3, 2026, 4:32 p.m.