Triple
T2219731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Morrison |
E48111
|
entity |
| Predicate | struckDown |
P25040
|
FINISHED |
| Object | 42 U.S.C. § 13981 |
—
|
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: 42 U.S.C. § 13981 | Statement: [United States v. Morrison, struckDown, 42 U.S.C. § 13981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: struckDown Context triple: [United States v. Morrison, struckDown, 42 U.S.C. § 13981]
-
A.
struckDownProvision
chosen
Indicates that a legal authority has invalidated or nullified a specific provision, rendering it without legal effect.
-
B.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
C.
stricken
Indicates that an entity has been severely affected, harmed, or afflicted by something (such as illness, disaster, or misfortune).
-
D.
fallsDownBefore
Indicates that one event or entity moves downward or collapses prior in time to another specified event or entity.
-
E.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of another entity.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc01386588190a9507f2969a201ca |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.