Triple
T896113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 14971:2019 |
E19349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | edition of ISO 14971 |
C5594
|
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: edition of ISO 14971 Context triple: [ISO 14971:2019, instanceOf, edition of ISO 14971]
-
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.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
C.
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.
-
D.
World Health Organization framework
The World Health Organization framework is a structured, evidence-based model that guides global health policy, planning, and interventions by organizing key determinants, systems, and outcomes to improve population health and equity.
-
E.
W3C specification maturity level
The W3C specification maturity level represents the formal stage in the World Wide Web Consortium’s standardization process that indicates how stable, reviewed, and implementation-ready a web technology specification is.
- F. None of above. chosen
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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.