Triple
T18372191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldred v. Ashcroft |
E446207
|
entity |
| Predicate | lowerCourtDecisionCitation |
P13941
|
FINISHED |
| Object | 239 F.3d 372 |
—
|
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: 239 F.3d 372 | Statement: [Eldred v. Ashcroft, lowerCourtDecisionCitation, 239 F.3d 372]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerCourtDecisionCitation Context triple: [Eldred v. Ashcroft, lowerCourtDecisionCitation, 239 F.3d 372]
-
A.
lowerCourtCitation
chosen
Indicates that a legal decision or document cites or references a ruling from a lower court.
-
B.
hasLowerCourtDecision
Indicates that a higher court case is associated with, or results from, a specific decision made by a lower court.
-
C.
lowerCourtCase
Indicates that one legal case is associated with, or arises from, proceedings in a lower court relative to another case.
-
D.
lowerCourt
Indicates that one court holds a subordinate or inferior position in the judicial hierarchy relative to another court.
-
E.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51754539c819083f13b85cacb6cce |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:44 a.m.