Triple
T642807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheney v. U.S. District Court for the District of Columbia |
E16775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | separation of powers case |
C734
|
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: separation of powers case Context triple: [Cheney v. U.S. District Court for the District of Columbia, instanceOf, separation of powers case]
-
A.
constitutional law case
chosen
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.
-
B.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
-
C.
branch of government
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
-
D.
supreme court
The Supreme Court is the highest judicial authority in a legal system, responsible for interpreting the constitution, resolving significant legal disputes, and setting binding precedents for lower courts.
-
E.
division of the United States Capitol Police
A division of the United States Capitol Police is an organizational unit within the agency responsible for specific protective, law enforcement, or administrative functions related to safeguarding the U.S. Capitol complex and its occupants.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.