Triple
T37508799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 9.2 Eternity’s End |
E932163
|
entity |
| Predicate | raidFinalBoss |
P100037
|
FINISHED |
| Object | The Jailer |
—
|
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: The Jailer | Statement: [Patch 9.2 Eternity’s End, raidFinalBoss, The Jailer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidFinalBoss Context triple: [Patch 9.2 Eternity’s End, raidFinalBoss, The Jailer]
-
A.
finalBossOf
chosen
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
-
B.
stageBossOf
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
C.
timeOfFinalBattle
Indicates the specific point in time at which the final or decisive battle takes place.
-
D.
finalRaidEncounter
Indicates that an encounter represents the ultimate or concluding boss fight or challenge within a raid.
-
E.
finalSmash
Indicates that one entity performs or activates a powerful, ultimate special attack or finishing move directed at another entity.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.