Triple
T23592018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of the United States (rulemaking under the Rules Enabling Act) |
E582506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal rulemaking authority |
C1181
|
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: federal rulemaking authority Context triple: [Supreme Court of the United States (rulemaking under the Rules Enabling Act), instanceOf, federal rulemaking authority]
-
A.
federal law
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
-
B.
federal power
Federal power is the authority and capacity vested in a national government to create, implement, and enforce laws and policies over its constituent states or regions within the limits set by a constitution.
-
C.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
D.
federal policy implementation
Federal policy implementation is the process by which national laws, regulations, and directives are translated into concrete programs, actions, and outcomes through coordination among government agencies, stakeholders, and enforcement mechanisms.
-
E.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:42 p.m.