Triple
T699592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | substantial effects doctrine |
E13968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States constitutional law concept |
C2144
|
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: United States constitutional law concept Context triple: [substantial effects doctrine, instanceOf, United States constitutional law concept]
-
A.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
B.
constitutional concept
chosen
A constitutional concept is an abstract legal and political idea that defines, structures, or constrains the organization, powers, and fundamental principles of a constitutional system.
-
C.
constitutional law
Constitutional law is the body of legal principles and rules that defines the structure, powers, and limits of government and protects fundamental rights under a nation's constitution.
-
D.
United States federal law instrument
A United States federal law instrument is an official legal document or mechanism, such as a statute, regulation, executive order, or treaty, through which the federal government creates, modifies, or enforces legal obligations and 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.