Triple
T37539171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpentshrine Cavern |
E933281
|
entity |
| Predicate | raidDifficulty |
P2406
|
FINISHED |
| Object | 25-player only (originally) |
—
|
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: 25-player only (originally) | Statement: [Serpentshrine Cavern, raidDifficulty, 25-player only (originally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidDifficulty Context triple: [Serpentshrine Cavern, raidDifficulty, 25-player only (originally)]
-
A.
raidDifficultyAvailability
Indicates how the availability or accessibility of a raid changes based on its selected difficulty level.
-
B.
raidProgressionTier
Indicates the specific tier or stage of advancement an entity has reached within a raid progression system.
-
C.
difficultyTargetBits
Indicates the required difficulty level for a task or computation, expressed as a target number of leading zero bits that a valid solution must satisfy.
-
D.
difficulty
chosen
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
E.
difficultySystem
Indicates a relationship where a system is characterized or classified by its level of difficulty.
- 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_69f76ec999288190ae26ec7b6aea7046 |
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. |
Created at: May 3, 2026, 4:17 p.m.