Triple
T38583998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isle of Quel'Danas |
E932304
|
entity |
| Predicate | raidEndBoss |
P100037
|
FINISHED |
| Object | Kil'jaeden |
—
|
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: Kil'jaeden | Statement: [Isle of Quel'Danas, raidEndBoss, Kil'jaeden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidEndBoss Context triple: [Isle of Quel'Danas, raidEndBoss, Kil'jaeden]
-
A.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
B.
finalBossOf
chosen
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
-
C.
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.
-
D.
raidConductedBy
Indicates that a particular raid was carried out or executed by a specified agent or organization.
-
E.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.