Triple
T4594635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buck v. Bell opinion |
E103577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark case in American constitutional law |
C732
|
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: landmark case in American constitutional law Context triple: [Buck v. Bell opinion, instanceOf, landmark case in American constitutional law]
-
A.
United States Supreme Court case
chosen
A United States Supreme Court case is a legal dispute brought before the highest federal court in the U.S., resulting in a binding decision that interprets the Constitution, federal laws, or treaties and sets nationwide precedent.
-
B.
landmark case
A landmark case is a court decision that establishes a significant new legal principle or precedent, often reshaping the interpretation or application of the law.
-
C.
constitutional law case
A constitutional law case is a legal dispute that requires a court to interpret and apply a nation's constitution to determine the validity of government actions, laws, or policies.
-
D.
constitutional law topic
A constitutional law topic is a specific subject area concerning the interpretation, application, or structure of a nation's constitution, including the distribution of governmental powers and the protection of individual rights.
-
E.
United States legal history event
A United States legal history event is a significant occurrence—such as a court decision, statute, constitutional amendment, or legal controversy—that materially shaped the development, interpretation, or application of American law.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:11 p.m.