Triple
T36671185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EC) No 178/2002 |
E905420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU food law |
C50219
|
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: EU food law Context triple: [Regulation (EC) No 178/2002, instanceOf, EU food law]
-
A.
food law
chosen
Food law is the body of legal rules, regulations, and policies that govern the production, processing, distribution, labeling, safety, and marketing of food to protect public health and ensure fair practices in the food system.
-
B.
European Union regulation
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
C.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
D.
EFSA body
An EFSA body is an organizational unit or panel within the European Food Safety Authority responsible for providing independent scientific advice and risk assessments on food and feed safety issues.
-
E.
United States food safety regulation
United States food safety regulation encompasses the laws, standards, and enforcement mechanisms—primarily administered by agencies such as the FDA and USDA—that govern the production, processing, distribution, and labeling of food to protect public health.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.