Triple
T7397455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scopes v. State |
E170656
|
entity |
| Predicate | reasonForReversal |
P76351
|
FINISHED |
| Object | improper jury sentencing of fine |
—
|
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: improper jury sentencing of fine | Statement: [Scopes v. State, reasonForReversal, improper jury sentencing of fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForReversal Context triple: [Scopes v. State, reasonForReversal, improper jury sentencing of fine]
-
A.
reasonForReturn
Indicates the reason or cause why an item, product, or entity is being sent back or returned.
-
B.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
C.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
-
D.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
E.
reasonForDismissal
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
- F. None of above. chosen
Provenance (4 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24abcd08190b8428fa22b2fbd4f |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:09 p.m.