Triple
T29054029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironclad Oath |
E735339
|
entity |
| Predicate | notableRelatedCase |
—
|
GENERATED |
| Object | Ex parte Garland |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelatedCase Context triple: [Ironclad Oath, notableRelatedCase, Ex parte Garland]
-
A.
relatedCase
chosen
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
B.
notableCaseContext
Indicates that an entity is associated with a particular contextual detail, circumstance, or background information relevant to a notable case or instance.
-
C.
notableSupremeCourtCase
Indicates that a legal case is recognized as a significant or influential decision by the Supreme Court.
-
D.
associatedCourtCase
Indicates a relationship where one entity is linked to, or involved in, a particular court case.
-
E.
notableCaseArea
Indicates that a particular geographic area is notably associated with, or significantly involved in, a given case or legal matter.
- F. None of above.
Provenance (1 batch)
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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:10 a.m.