Triple
T25784483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apprendi v. New Jersey |
E649382
|
entity |
| Predicate | overruledOrLimitedPrecedent |
P18493
|
FINISHED |
| Object | McMillan v. Pennsylvania |
—
|
NE NERFINISHED |
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: McMillan v. Pennsylvania | Statement: [Apprendi v. New Jersey, overruledOrLimitedPrecedent, McMillan v. Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overruledOrLimitedPrecedent Context triple: [Apprendi v. New Jersey, overruledOrLimitedPrecedent, McMillan v. Pennsylvania]
-
A.
overruledByStatute
Indicates that a legal rule, decision, or principle has been superseded or invalidated by a later-enacted statute.
-
B.
overturnedDecisionOf
Indicates that one decision reversed, nullified, or set aside a previous decision.
-
C.
overturnedLaw
Indicates that a previously established law has been invalidated or reversed, typically by a higher legal authority or court decision.
-
D.
wasOverturnedByCourt
Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
-
E.
overturnedInPartBy
chosen
Indicates that a prior decision, ruling, or outcome has been partially reversed or modified by a later authority or action.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fef935a8819083bc9cefa4a72f8e |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:53 a.m.