Triple
T16434646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of the State of California |
E399150
|
entity |
| Predicate | roleInCriminalLaw |
P52875
|
FINISHED |
| Object | prosecution of crimes |
—
|
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: prosecution of crimes | Statement: [People of the State of California, roleInCriminalLaw, prosecution of crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCriminalLaw Context triple: [People of the State of California, roleInCriminalLaw, prosecution of crimes]
-
A.
roleInCrime
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
B.
roleInInvestigation
Indicates that an entity holds a specific function, capacity, or responsibility within the context of a particular investigation.
-
C.
haveCriminalLaw
chosen
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
D.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
E.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba1023481909588aa6a3c677886 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.