Triple
T11755807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court affirmed reversal of conviction |
E279521
|
entity |
| Predicate | effectOnDefendant |
P90225
|
FINISHED |
| Object | conviction overturned |
—
|
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: conviction overturned | Statement: [Supreme Court affirmed reversal of conviction, effectOnDefendant, conviction overturned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnDefendant Context triple: [Supreme Court affirmed reversal of conviction, effectOnDefendant, conviction overturned]
-
A.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
effectOnLitigation
chosen
Indicates the impact or influence that one factor, event, or condition has on the course, strategy, or outcome of legal proceedings.
-
C.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case or proceeding.
-
D.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
E.
defendantPosition
Indicates the role, stance, or location that a defendant holds within a legal case or proceeding.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50c8d708190ad79ecb57b715d04 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.