Triple

T5433096
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 24748-1 E121542 entity
Predicate relatesToStandard P19701 FINISHED
Object ISO/IEC 15288 E21930 NE FINISHED

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/IEC 15288 | Statement: [ISO/IEC 24748-1, relatesToStandard, ISO/IEC 15288]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO/IEC 15288
Context triple: [ISO/IEC 24748-1, relatesToStandard, ISO/IEC 15288]
  • A. ISO/IEC 15288 chosen
    ISO/IEC 15288 is an international standard that defines a common framework of processes for the life cycle management of systems, from conception through retirement.
  • B. 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.
  • C. IEEE 12207
    IEEE 12207 is an international standard that defines processes, activities, and tasks 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. ISO/IEC 24748
    ISO/IEC 24748 is an international standard that provides guidance on the application and management of systems and software life cycle processes defined in standards such as ISO/IEC 15288.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd463c65f0819082ee6483ab4b466a completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd964583008190bf7b94f656e4ecf2 completed March 20, 2026, 6:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf41284998819096667ae70180e067 completed March 22, 2026, 1:08 a.m.
Created at: March 20, 2026, 2:06 p.m.