Triple
T10975445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilderoy Lockhart |
E259357
|
entity |
| Predicate | spellBackfired |
P37388
|
FINISHED |
| Object | Obliviate |
—
|
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: Obliviate | Statement: [Gilderoy Lockhart, spellBackfired, Obliviate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spellBackfired Context triple: [Gilderoy Lockhart, spellBackfired, Obliviate]
-
A.
attemptedCurseReversal
Indicates an action where one entity tried, but did not necessarily succeed, to reverse or undo a curse affecting another entity.
-
B.
speechAbilityBeforeCurse
Indicates that an entity possessed the ability to speak prior to being affected by a specific curse.
-
C.
callsLosersBack
Indicates that an entity initiates a follow-up contact or response specifically to those entities that previously lost or were unsuccessful.
-
D.
spokenIncantation
chosen
Indicates that an entity has uttered a specific magical or ritual phrase, typically to invoke an effect or power.
-
E.
inventedSpell
Indicates that one entity is the creator or originator of a particular spell used or known by another entity.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f4e888819097433271a2f45ff3 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.