Triple

T4617152
Position Surface form Disambiguated ID Type / Status
Subject ISO Guide 73 E100894 entity
Predicate supportsStandard P1587 FINISHED
Object ISO 31000 E18758 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 31000 | Statement: [ISO Guide 73, supportsStandard, ISO 31000]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 31000
Context triple: [ISO Guide 73, supportsStandard, ISO 31000]
  • A. ISO 31000 chosen
    ISO 31000 is an international standard that provides principles and guidelines for effective risk management applicable to organizations of all types and sizes.
  • B. ISO 31010
    ISO 31010 is an international standard that provides guidelines and a comprehensive toolkit of techniques for risk assessment within risk management frameworks.
  • C. ISO 22301
    ISO 22301 is an international standard that specifies requirements for establishing, implementing, maintaining, and improving a business continuity management system.
  • D. ISO/IEC 27005
    ISO/IEC 27005 is an international standard that provides guidelines for information security risk management within an organization’s overall information security management system.
  • E. ISO/IEC 27000 family
    The ISO/IEC 27000 family is an international set of standards that provides best-practice frameworks and requirements for establishing, implementing, maintaining, and continually improving information security management systems.
  • 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_69bd43cf363c819087fd5ab441b4a3f4 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd59e098c08190b769e76937dff700 completed March 20, 2026, 2:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4390976c81908ab31c4e25f96064 completed March 21, 2026, 7:06 a.m.
Created at: March 20, 2026, 1:12 p.m.