Triple
T38645346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun King’s Salvation |
E938699
|
entity |
| Predicate | bossName |
P114830
|
FINISHED |
| Object | Kael’thas Sunstrider |
—
|
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: Kael’thas Sunstrider | Statement: [Sun King’s Salvation, bossName, Kael’thas Sunstrider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossName Context triple: [Sun King’s Salvation, bossName, Kael’thas Sunstrider]
-
A.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
B.
enemyName
Indicates that the specified name is the designated enemy of a given 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
chosen
Indicates a relationship where one entity is the boss or superior of another within a fictional or imagined context.
-
E.
dropBoss
Indicates that one entity dismisses, removes, or ceases to support another entity who holds a position of authority or leadership.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.