Triple
T14987361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Roberts |
E373738
|
entity |
| Predicate | helpsProsecute |
P116234
|
FINISHED |
| Object | corrupt police officers |
—
|
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: corrupt police officers | Statement: [Richie Roberts, helpsProsecute, corrupt police officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsProsecute Context triple: [Richie Roberts, helpsProsecute, corrupt police officers]
-
A.
counselForProsecution
Indicates that an entity serves as a legal representative or advisor acting on behalf of the prosecution in a legal proceeding.
-
B.
prosecuted
Indicates that legal authorities have formally brought criminal charges against an entity and pursued a case against them in a court of law.
-
C.
mayProsecute
Indicates that one party has the legal authority or permission to initiate and conduct prosecution against another party.
-
D.
subsequentProsecutor
Indicates that one prosecutor follows or succeeds another in handling the same or a related legal case.
-
E.
subjectOfProsecution
Indicates that an entity is the target or focus of a legal prosecution or criminal proceeding initiated by an authority.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7007588819095bb1de029a6f2eb |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:53 a.m.