Triple
T5111013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sirius Black |
E115212
|
entity |
| Predicate | wronglyAccusedOf |
P9856
|
FINISHED |
| Object | betraying James and Lily Potter |
—
|
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: betraying James and Lily Potter | Statement: [Sirius Black, wronglyAccusedOf, betraying James and Lily Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wronglyAccusedOf Context triple: [Sirius Black, wronglyAccusedOf, betraying James and Lily Potter]
-
A.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
-
B.
accusedOf
chosen
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
D.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
-
E.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.