Triple

T7896685
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 24744 E183356 entity
Predicate hasAbbreviation P43 FINISHED
Object ISO 24744 E183356 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 24744 | Statement: [ISO/IEC 24744, hasAbbreviation, ISO 24744]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 24744
Context triple: [ISO/IEC 24744, hasAbbreviation, ISO 24744]
  • A. ISO/IEC 24744 chosen
    ISO/IEC 24744 is an international standard that defines a metamodel and framework for modeling and engineering software development methodologies.
  • B. 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.
  • C. ISO/IEC 23272
    ISO/IEC 23272 is an international standard in the joint ISO/IEC series that specifies technical requirements and guidelines in the field of information and communication technologies.
  • D. ISO/IEC 10514
    ISO/IEC 10514 is the international standard that formally defines the syntax and semantics of the Modula-2 programming language.
  • E. ISO 26324
    ISO 26324 is the international standard that defines the structure, syntax, and functional framework of the Digital Object Identifier (DOI) system for uniquely identifying digital content.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a187a0081909a0c0822c6dab1da completed March 31, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5bb24c8c8190860e4dd1d705b04b completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5:01 p.m.