Triple
T21850103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Prison Camp Montgomery |
E539480
|
entity |
| Predicate | primaryOffenseType |
P7957
|
FINISHED |
| Object | non-violent offenses |
—
|
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: non-violent offenses | Statement: [Federal Prison Camp Montgomery, primaryOffenseType, non-violent offenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOffenseType Context triple: [Federal Prison Camp Montgomery, primaryOffenseType, non-violent offenses]
-
A.
criminalType
Indicates the specific category or classification of crime associated with a criminal act or offender.
-
B.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
-
D.
crimeType
chosen
Indicates the specific category or nature of the crime associated with an event or entity.
-
E.
offenceCognizable
Indicates that the offence is of a type for which police may initiate investigation and arrest without requiring prior permission or a warrant from a magistrate.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd582ca48190890648fdee2a0c6e |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.