Triple
T868408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 13485 |
E18757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical device standard |
C2538
|
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: medical device standard Context triple: [ISO 13485, instanceOf, medical device 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.
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.
engineering standard
chosen
An engineering standard is a documented set of agreed-upon technical criteria, methods, and requirements intended to ensure safety, interoperability, quality, and consistency in engineering design, production, and operation.
-
D.
software standard
A software standard is an agreed-upon set of rules, formats, and practices that ensures compatibility, interoperability, and quality across different software systems and components.
-
E.
technical standards body
A technical standards body is an organization that develops, maintains, and promotes agreed-upon technical specifications and protocols to ensure interoperability, safety, and consistency across industries and technologies.
- 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.