Triple
T30345963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illyasviel von Einzbern |
E771868
|
entity |
| Predicate | hasCommandSpellsOn |
P203191
|
FINISHED |
| Object | Berserker (Heracles) |
—
|
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: Berserker (Heracles) | Statement: [Illyasviel von Einzbern, hasCommandSpellsOn, Berserker (Heracles)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandSpellsOn Context triple: [Illyasviel von Einzbern, hasCommandSpellsOn, Berserker (Heracles)]
-
A.
canCastSpells
Indicates that an entity possesses the ability to perform or use spells.
-
B.
hasAssociatedSpell
Indicates that an entity is linked to or accompanied by a specific spell.
-
C.
commandSpellHolder
Indicates that one entity exerts control over another entity that holds or maintains a spell, directing or influencing how that spell is used or managed.
-
D.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
E.
hasMagicPractitioner
Indicates that an entity is associated with or utilizes the services of a magic practitioner.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01378bf05c8190af9f5e06a2810c7d |
completed | May 11, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_6a0137277c6c8190bcec341f2a0757c4 |
completed | May 11, 2026, 1:55 a.m. |
| PDg | Predicate description generation | batch_6a01378b165c8190b7b738da4e1ab36b |
completed | May 11, 2026, 1:57 a.m. |
Created at: April 29, 2026, 7:55 p.m.