Triple
T868263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 22000 |
E18754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | food safety management standard |
C4305
|
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 management standard Context triple: [ISO 22000, instanceOf, food safety management standard]
-
A.
military standard
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
B.
software review and audit standard
A software review and audit standard is a formalized set of criteria, processes, and guidelines used to systematically evaluate software products and development practices for quality, compliance, security, and reliability.
-
C.
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.
-
D.
official standard
chosen
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
-
E.
WHO framework
The WHO framework is a structured, evidence-based model developed by the World Health Organization to guide global health policy, planning, and interventions across health systems, disease control, and population well-being.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.