Triple
T1538996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schenck v. United States |
E32820
|
entity |
| Predicate | lowerCourtOutcome |
P19102
|
FINISHED |
| Object | conviction affirmed |
—
|
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 affirmed | Statement: [Schenck v. United States, lowerCourtOutcome, conviction affirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerCourtOutcome Context triple: [Schenck v. United States, lowerCourtOutcome, conviction affirmed]
-
A.
lowerCourt
Indicates that one court holds a subordinate or inferior position in the judicial hierarchy relative to another court.
-
B.
lowerCourtCitation
Indicates that a legal decision or document cites or references a ruling from a lower court.
-
C.
hasLowerCourtDecision
chosen
Indicates that a higher court case is associated with, or results from, a specific decision made by a lower court.
-
D.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
E.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a915f323bc8190aa757142c225e0ae |
completed | March 5, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69a907b046448190be8ea4d7b20255f7 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.