Triple
T20210202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dementor’s Kiss |
E493468
|
entity |
| Predicate | threatenedAgainst |
P956
|
FINISHED |
| Object | Sirius Black at Hogwarts lake |
—
|
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: Sirius Black at Hogwarts lake | Statement: [Dementor’s Kiss, threatenedAgainst, Sirius Black at Hogwarts lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatenedAgainst Context triple: [Dementor’s Kiss, threatenedAgainst, Sirius Black at Hogwarts lake]
-
A.
threatenedVictim
Indicates that one entity has issued or posed a threat of harm or adverse consequences toward another entity.
-
B.
threatenedBy
chosen
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
D.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
E.
isThreatenedCategory
Indicates that an entity belongs to a category facing risk of harm, decline, or extinction.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.