Triple
T37554100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majordomo Executus |
E933652
|
entity |
| Predicate | bossOrderInRaid |
P188726
|
FINISHED |
| Object | Penultimate boss of Molten Core |
—
|
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: Penultimate boss of Molten Core | Statement: [Majordomo Executus, bossOrderInRaid, Penultimate boss of Molten Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossOrderInRaid Context triple: [Majordomo Executus, bossOrderInRaid, Penultimate boss of Molten Core]
-
A.
bossOrder
Indicates that a boss issues a directive or command to a subordinate.
-
B.
missionOrder
Indicates that one mission is ordered, sequenced, or prioritized relative to another within an overall mission plan.
-
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.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
-
E.
questOrderedBy
Indicates that one entity is a quest that has been requested, assigned, or commissioned by another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.