Triple
T27173426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevron deference |
E682979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States administrative law doctrine |
C250
|
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 administrative law doctrine Context triple: [Chevron deference, instanceOf, United States administrative law doctrine]
-
A.
administrative law case
An administrative law case is a legal dispute that arises from actions or decisions of government agencies, focusing on the interpretation, application, or validity of administrative rules and procedures.
-
B.
administrative law scholar
An administrative law scholar is a legal expert who studies, analyzes, and critiques the structures, procedures, and decisions of administrative agencies and their role in governance.
-
C.
branch of administrative law
A branch of administrative law is a specialized area within the broader field that governs the organization, powers, procedures, and accountability of public administrative agencies in a particular domain (such as environmental regulation, immigration, or social welfare).
-
D.
state action doctrine
The state action doctrine is a legal principle that limits constitutional protections—particularly under the U.S. Constitution—to actions fairly attributable to the government, rather than purely private conduct.
-
E.
United States federal law
chosen
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.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:24 a.m.