Triple
T37705111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungering Destroyer |
E939177
|
entity |
| Predicate | raidSizeModes |
P188353
|
FINISHED |
| Object | 10–30 players (flex) in Normal |
—
|
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: 10–30 players (flex) in Normal | Statement: [Hungering Destroyer, raidSizeModes, 10–30 players (flex) in Normal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidSizeModes Context triple: [Hungering Destroyer, raidSizeModes, 10–30 players (flex) in Normal]
-
A.
raidSize
Indicates the number of participants or units involved in a single raid event.
-
B.
raidSizeSupport
Indicates the extent to which one entity supports, enables, or is compatible with a particular RAID configuration size.
-
C.
raidSizeReworked
Indicates that the size or composition of a raid has been modified or recalculated from its original configuration.
-
D.
raidSizeVersions
chosen
Indicates the different size configurations or capacities available across versions of a RAID setup.
-
E.
raidSizeOriginal
Indicates the original number of participants or units involved in a raid before any changes or adjustments.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.