Triple
T25614845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intentional Adulteration (food defense) rule |
E642129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | food defense regulation |
C10033
|
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 defense regulation Context triple: [Intentional Adulteration (food defense) rule, instanceOf, food defense regulation]
-
A.
food safety organization
A food safety organization is an entity responsible for developing, implementing, and enforcing standards, regulations, and practices to ensure that food is safe, hygienic, and free from harmful contaminants throughout the supply chain.
-
B.
agricultural import enforcement program
An agricultural import enforcement program is a regulatory framework that monitors, inspects, and controls incoming agricultural products to prevent pests, diseases, and non-compliant goods from entering a country’s markets and ecosystems.
-
C.
food security platform
A food security platform is a digital system that connects producers, distributors, and consumers to monitor, manage, and ensure reliable access to safe, nutritious, and affordable food.
-
D.
safety regulation
chosen
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.
-
E.
public health regulation
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.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 4:59 p.m.