Triple
T26104798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Blue Death |
E658507
|
entity |
| Predicate | hasProtagonistClass |
P185186
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [Berserker Blue Death, hasProtagonistClass, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistClass Context triple: [Berserker Blue Death, hasProtagonistClass, humans]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasSpiritProtagonist
Indicates that the primary or central character in a narrative is a spirit or non-corporeal being.
-
C.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
-
D.
hasFranchiseProtagonistTrait
Indicates that a protagonist in a franchise possesses a specific recurring trait or characteristic associated with that franchise.
-
E.
hasChampionClass
Indicates that an entity is associated with, or belongs to, a particular champion class or category.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 26, 2026, 7:57 p.m.