Triple
T38437129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zivotofsky v. Clinton |
E903976
|
entity |
| Predicate | subsequentRelatedCaseCitation |
P3137
|
FINISHED |
| Object | 576 U.S. 1 |
—
|
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: 576 U.S. 1 | Statement: [Zivotofsky v. Clinton, subsequentRelatedCaseCitation, 576 U.S. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentRelatedCaseCitation Context triple: [Zivotofsky v. Clinton, subsequentRelatedCaseCitation, 576 U.S. 1]
-
A.
subsequentCitationAsPrecedentFor
Indicates that one citation is used later as a precedent or authoritative basis for another citation or legal decision.
-
B.
subsequentCase
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
-
C.
subsequentCitationIn
Indicates that one work cites or references another work that appears later in a specified source or sequence.
-
D.
subsequentCitationBy
Indicates that one work is cited by another work that was produced or published at a later time.
-
E.
relatedCase
chosen
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.