Triple
T24395419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan v. Virginia Railway Co. (1938) |
E615014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hughes Court decision |
C4529
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hughes Court decision Context triple: [Morgan v. Virginia Railway Co. (1938), instanceOf, Hughes Court decision]
-
A.
Insular Cases decision
An Insular Cases decision is a U.S. Supreme Court ruling from the early 20th century that determined how the Constitution applies to territories acquired by the United States, distinguishing between "incorporated" and "unincorporated" territories.
-
B.
court decision
chosen
A court decision is a formal, authoritative ruling issued by a judicial body that resolves the legal issues in a case and may establish or apply legal precedent.
-
C.
Supreme Court footnote
A Supreme Court footnote is a subordinate textual annotation in a Court opinion that provides clarification, limitation, or additional reasoning that can significantly influence the interpretation and scope of the decision.
-
D.
Insular Case
Insular Case is a legal concept representing a self-contained, jurisdictionally isolated legal matter or dispute whose rules, procedures, and consequences are largely unaffected by external legal systems or broader precedents.
-
E.
Erie doctrine case
An Erie doctrine case is a federal court lawsuit in which the court must decide whether to apply state substantive law or federal law/procedural rules under the principles established in Erie Railroad Co. v. Tompkins and its progeny.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:04 a.m.