Triple
T30440431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soham murders |
E774424
|
entity |
| Predicate | coAccusedVerdict |
P170222
|
FINISHED |
| Object | guilty of perverting the course of justice |
—
|
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: guilty of perverting the course of justice | Statement: [Soham murders, coAccusedVerdict, guilty of perverting the course of justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coAccusedVerdict Context triple: [Soham murders, coAccusedVerdict, guilty of perverting the course of justice]
-
A.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
B.
resultOfAccusation
Indicates that one entity is the outcome, consequence, or product of an accusation made by another entity.
-
C.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
D.
coAccusedInCaseWith
Indicates that two or more entities are jointly accused as defendants in the same legal case.
-
E.
victimOfAccusation
Indicates that an entity is the target or subject of an accusation made by another party.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:08 p.m.