Triple
T12527824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberts v. Louisiana |
E299483
|
entity |
| Predicate | postFurmanCase |
P39290
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Roberts v. Louisiana, postFurmanCase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postFurmanCase Context triple: [Roberts v. Louisiana, postFurmanCase, true]
-
A.
postFurman
chosen
Indicates that something occurs, applies, or is evaluated after the U.S. Supreme Court’s decision in *Furman v. Georgia* (i.e., in the post-*Furman* legal context).
-
B.
laterCourt
Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
-
C.
postEpsteinStatus
Indicates that an entity publicly shares or updates information about Jeffrey Epstein’s situation or case status.
-
D.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
courtReview
Indicates that a court formally examines a decision, action, or case to determine its legality, correctness, or appropriateness.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.