Triple
T27873805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Justice Division (Oregon DOJ) |
E704870
|
entity |
| Predicate | typeOfCrimesHandled |
P31978
|
FINISHED |
| Object | major 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: major crimes | Statement: [Criminal Justice Division (Oregon DOJ), typeOfCrimesHandled, major crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCrimesHandled Context triple: [Criminal Justice Division (Oregon DOJ), typeOfCrimesHandled, major crimes]
-
A.
typeOfCasesHandled
chosen
Indicates the categories or kinds of cases that an entity (such as a person, organization, or system) is responsible for managing or processing.
-
B.
handledCrimes
Indicates that an entity (such as a person or organization) took responsibility for dealing with, investigating, or managing specific crimes.
-
C.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
D.
perpetratedCrimesIn
Indicates that an entity committed one or more crimes within a specified location or jurisdiction.
-
E.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 6:26 p.m.