Triple
T38588792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icecrown Gunship Battle |
E932405
|
entity |
| Predicate | bossNPC |
P126648
|
FINISHED |
| Object | Muradin Bronzebeard |
—
|
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: Muradin Bronzebeard | Statement: [Icecrown Gunship Battle, bossNPC, Muradin Bronzebeard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossNPC Context triple: [Icecrown Gunship Battle, bossNPC, Muradin Bronzebeard]
-
A.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
B.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
C.
fictionalBossOf
Indicates a relationship where one entity is the boss or superior of another within a fictional or imagined context.
-
D.
stageBossOf
chosen
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
E.
bossOrder
Indicates that a boss issues a directive or command to a subordinate.
- 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.