Triple
T19259548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC standards |
E481608
|
entity |
| Predicate | include |
P1393
|
FINISHED |
| Object | IEC 62304 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: IEC 62304 | Statement: [IEC standards, include, IEC 62304]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEC 62304 Context triple: [IEC standards, include, IEC 62304]
-
A.
IEC 62304
chosen
IEC 62304 is an international standard that defines life cycle requirements for the development and maintenance of medical device software.
-
B.
ISO 14971
ISO 14971 is an international standard that specifies a systematic process for risk management of medical devices throughout their life cycle.
-
C.
IEC 60601-1
IEC 60601-1 is an international standard that specifies general safety and essential performance requirements for medical electrical equipment and systems.
-
D.
IEC 60601
IEC 60601 is an international standard that specifies safety and essential performance requirements for medical electrical equipment.
-
E.
ISO 13485
ISO 13485 is an international quality management standard that specifies requirements for organizations involved in the design, production, installation, and servicing of medical devices and related services.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8858588190a04e2a01e43fb7b2 |
completed | April 20, 2026, 10:10 a.m. |
Created at: April 10, 2026, 1:28 p.m.