Triple

T22185680
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 12182 E548289 entity
Predicate standardFamily P751 FINISHED
Object ISO/IEC software and systems engineering standards NE NERFINISHED

How this triple was built (3 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/IEC software and systems engineering standards | Statement: [ISO/IEC 12182, standardFamily, ISO/IEC software and systems engineering standards]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO/IEC software and systems engineering standards
Context triple: [ISO/IEC 12182, standardFamily, ISO/IEC software and systems engineering standards]
  • A. IEEE software engineering standards collection
    The IEEE software engineering standards collection is a comprehensive set of internationally recognized guidelines and best practices that define processes, documentation, and quality criteria across the software development lifecycle.
  • B. ISO/IEC 25000 series
    The ISO/IEC 25000 series is an international set of standards that defines models, measures, and evaluation processes for software product quality and data quality within the SQuaRE (Software product Quality Requirements and Evaluation) framework.
  • C. ISO/IEC 12207
    ISO/IEC 12207 is an international standard that defines a comprehensive framework and set of processes for the life cycle management of software systems.
  • D. ISO/IEC/IEEE 29148
    ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
  • E. IEEE 12207
    IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: ISO/IEC software and systems engineering standards
Target entity description: ISO/IEC software and systems engineering standards are an internationally recognized family of standards that define best practices, processes, and terminology for the engineering, management, and lifecycle of software and systems.
  • A. IEEE software engineering standards collection
    The IEEE software engineering standards collection is a comprehensive set of internationally recognized guidelines and best practices that define processes, documentation, and quality criteria across the software development lifecycle.
  • B. ISO/IEC 25000 series
    The ISO/IEC 25000 series is an international set of standards that defines models, measures, and evaluation processes for software product quality and data quality within the SQuaRE (Software product Quality Requirements and Evaluation) framework.
  • C. ISO/IEC 12207 chosen
    ISO/IEC 12207 is an international standard that defines a comprehensive framework and set of processes for the life cycle management of software systems.
  • D. ISO/IEC/IEEE 29148
    ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
  • E. IEEE 12207
    IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
  • F. None of above.

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_69e11e3e0c7c8190b30d278845e2497e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12aa823888190829368de6db4aa91 completed April 28, 2026, 9:46 p.m.
Created at: April 16, 2026, 8:35 p.m.