Triple
T770544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trump v. Vance |
E16270
|
entity |
| Predicate | lowerCourtJudgment |
P2931
|
FINISHED |
| Object | 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: affirmed | Statement: [Trump v. Vance, lowerCourtJudgment, affirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerCourtJudgment Context triple: [Trump v. Vance, lowerCourtJudgment, 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.
trialCourt
Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
-
D.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
-
E.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a704fb148190b203a5bdd77e961c |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.