Triple
T28078505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Gementera |
E709612
|
entity |
| Predicate | sentencingObjective |
P47279
|
FINISHED |
| Object | deterrence |
—
|
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: deterrence | Statement: [United States v. Gementera, sentencingObjective, deterrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentencingObjective Context triple: [United States v. Gementera, sentencingObjective, deterrence]
-
A.
aimOfPunishment
chosen
Indicates that a specified purpose or objective is the intended goal or rationale behind a particular act of punishment.
-
B.
sentencedTo
Indicates that an authority has officially assigned a specific punishment or penalty to an entity, typically as the outcome of a legal or disciplinary process.
-
C.
sentencingYear
Indicates the calendar year in which a person or entity received a formal legal sentence or judgment.
-
D.
sentencedOn
Indicates that a judicial authority has formally imposed a legal sentence or punishment on an entity on a specific date.
-
E.
sentencingError
Indicates that there was a mistake or irregularity in the legal process of determining or imposing a sentence.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640428d988190992cf8e5455fc02c |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:50 p.m.