Triple
T14198538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 38 of the Code of Federal Regulations |
E351904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal administrative regulation |
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: federal administrative regulation Context triple: [Title 38 of the Code of Federal Regulations, instanceOf, federal administrative regulation]
-
A.
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.
-
B.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:04 a.m.