Triple

T3418809
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 14882 E72069 entity
Predicate hasEdition P35 FINISHED
Object ISO/IEC 14882:2011 E72069 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 14882:2011 | Statement: [ISO/IEC 14882, hasEdition, ISO/IEC 14882:2011]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO/IEC 14882:2011
Context triple: [ISO/IEC 14882, hasEdition, ISO/IEC 14882:2011]
  • A. ISO/IEC 14882 chosen
    ISO/IEC 14882 is the international standard that formally defines the C++ programming language, including its core language features and standard library.
  • B. ISO/IEC 9899
    ISO/IEC 9899 is the international standard that defines the C programming language’s syntax, semantics, and library.
  • C. The C++ Programming Language
    The C++ Programming Language is a comprehensive reference and tutorial book by Bjarne Stroustrup that defines, explains, and showcases the design and use of the C++ programming language.
  • D. ISO/IEC JTC 1 standard
    ISO/IEC 12207 is an international standard that defines processes, activities, and tasks for software life cycle management, from acquisition and development through operation and maintenance.
  • E. 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.
  • 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_69ad85ad38e48190b7660c5118a35289 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb92df1e48190bbf22a47e44579f1 completed March 8, 2026, 6 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360c285688190a264fcb4ab271b82 completed March 13, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:15 p.m.