Triple

T19558462
Position Surface form Disambiguated ID Type / Status
Subject IEC 60601 E489377 entity
Predicate relatedTo P37 FINISHED
Object ISO 14971 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: ISO 14971 | Statement: [IEC 60601, relatedTo, ISO 14971]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 14971
Context triple: [IEC 60601, relatedTo, ISO 14971]
  • A. ISO 14971 chosen
    ISO 14971 is an international standard that specifies a systematic process for risk management of medical devices throughout their life cycle.
  • B. 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.
  • C. IEC 62304
    IEC 62304 is an international standard that defines life cycle requirements for the development and maintenance of medical device software.
  • D. ICH Q9 Quality Risk Management
    ICH Q9 Quality Risk Management is an international guideline that provides a systematic, science- and risk-based approach to identifying, evaluating, and controlling quality risks throughout the lifecycle of pharmaceutical products.
  • E. ISO 10021
    ISO 10021 is an international standard that defines the Message Handling System (MHS) architecture and protocols for electronic mail in the OSI (Open Systems Interconnection) environment.
  • 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63f723d5081909553a4363b579a6b completed April 20, 2026, 3 p.m.
Created at: April 10, 2026, 1:42 p.m.