Triple
T4143597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King v. Burwell |
E89330
|
entity |
| Predicate | affirmedOrReversed |
P1123
|
FINISHED |
| Object | Fourth Circuit judgment 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: Fourth Circuit judgment affirmed | Statement: [King v. Burwell, affirmedOrReversed, Fourth Circuit judgment affirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affirmedOrReversed Context triple: [King v. Burwell, affirmedOrReversed, Fourth Circuit judgment affirmed]
-
A.
wasOverturnedByCourt
Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
-
B.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
C.
upheldBy
chosen
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
D.
overturnedDecisionOf
Indicates that one decision reversed, nullified, or set aside a previous decision.
-
E.
wasOverturnedInYear
Indicates that a prior decision, ruling, or outcome was reversed or nullified in the specified year.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.