Triple
T19113354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 32, Code of Federal Regulations (U.S.) |
E467844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | body of federal administrative regulations |
C31860
|
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: body of federal administrative regulations Context triple: [Title 32, Code of Federal Regulations (U.S.), instanceOf, body of federal administrative regulations]
-
A.
Code of Federal Regulations part
A Code of Federal Regulations part is a distinct subdivision within a CFR title that organizes and codifies a specific set of related federal rules and regulatory requirements.
-
B.
central government regulations
Central government regulations are legally binding rules and standards issued by national authorities to direct, control, and coordinate activities within a country in accordance with public policy and law.
-
C.
regulations
chosen
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
D.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
E.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:05 p.m.