Triple
T20364285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People of the State of New York |
E496864
|
entity |
| Predicate | roleInCriminalCases |
P46944
|
FINISHED |
| Object | prosecution |
—
|
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 | Statement: [People of the State of New York, roleInCriminalCases, prosecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCriminalCases Context triple: [People of the State of New York, roleInCriminalCases, prosecution]
-
A.
roleInCrime
chosen
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.
consideredCriminalBy
Indicates that one party regards or classifies another party as a criminal according to its own laws, rules, or judgments.
-
D.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
E.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786fd0088190908187ab642344cc |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:26 a.m.