Triple
T3745779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Branch |
E81206
|
entity |
| Predicate | typeOfOffense |
P7957
|
FINISHED |
| Object | quality-of-life misdemeanors |
—
|
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: quality-of-life misdemeanors | Statement: [Criminal Branch, typeOfOffense, quality-of-life misdemeanors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOffense Context triple: [Criminal Branch, typeOfOffense, quality-of-life misdemeanors]
-
A.
crimeType
chosen
Indicates the specific category or nature of the crime associated with an event or entity.
-
B.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
C.
definesOffence
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
-
D.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
-
E.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb680ddc819094205beb342699f9 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.