Triple
T37540636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N’Zoth, the Corruptor |
E933315
|
entity |
| Predicate | finalRaidBossOf |
P100037
|
FINISHED |
| Object | Ny’alotha, the Waking City |
—
|
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: Ny’alotha, the Waking City | Statement: [N’Zoth, the Corruptor, finalRaidBossOf, Ny’alotha, the Waking City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRaidBossOf Context triple: [N’Zoth, the Corruptor, finalRaidBossOf, Ny’alotha, the Waking City]
-
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.
finalRaidEncounter
Indicates that an encounter represents the ultimate or concluding boss fight or challenge within a raid.
-
C.
finalBossType
Indicates that an entity serves as the ultimate or final boss of another entity, specifying the type or category of that final boss.
-
D.
finalBossFaction
Indicates that an entity serves as or belongs to the faction of the ultimate or final boss in a game or narrative.
-
E.
finalBossRace
Indicates that the referenced race or species serves as the ultimate or final boss encounter in a game or narrative.
- 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_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:17 p.m.