Triple
T37539109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magtheridon's Lair |
E933280
|
entity |
| Predicate | finalBossType |
P199205
|
FINISHED |
| Object | pit lord |
—
|
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: pit lord | Statement: [Magtheridon's Lair, finalBossType, pit lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalBossType Context triple: [Magtheridon's Lair, finalBossType, pit lord]
-
A.
finalBossOf
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.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
D.
fictionalBossOf
Indicates a relationship where one entity is the boss or superior of another within a fictional or imagined context.
-
E.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69ff255abca881908ef7635bd2e5af98 |
completed | May 9, 2026, 12:15 p.m. |
Created at: May 3, 2026, 4:17 p.m.