Triple
T5323834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Meat Inspection Act |
E121739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | food safety law |
C3360
|
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: food safety law Context triple: [Federal Meat Inspection Act, instanceOf, food safety law]
-
A.
safety regulation
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
-
B.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
C.
public health regulation
chosen
Public health regulation is the body of laws, policies, and administrative rules designed to protect and promote population health by controlling risks, guiding health behaviors, and ensuring safe environments, products, and services.
-
D.
public health law
Public health law is the body of legal rules, powers, and duties that governments use to prevent disease, promote health, and protect populations while balancing individual rights and community interests.
-
E.
agricultural law
Agricultural law is the body of legal rules, regulations, and policies that govern farming activities, food production, land use, environmental impacts, and the rights and obligations of agricultural producers and related stakeholders.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.