Triple

T5362789
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 27000 family E103059 entity
Predicate definesConceptsIn P201 FINISHED
Object information security management systems LITERAL 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: information security management systems | Statement: [ISO/IEC 27000 family, definesConceptsIn, information security management systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesConceptsIn
Context triple: [ISO/IEC 27000 family, definesConceptsIn, information security management systems]
  • A. introducedConcept chosen
    Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
  • B. defendsConcept
    Indicates that one entity actively supports and argues in favor of a particular concept, idea, or theory, often in response to criticism or challenge.
  • C. hasConcept
    Indicates that an entity includes, embodies, or is associated with a particular concept.
  • D. definesAimsOf
    Indicates that one entity specifies or establishes the goals, purposes, or intended outcomes of another entity.
  • E. operationalConcept
    Indicates that one entity defines, specifies, or embodies the operational concept or way of functioning for another entity.
  • F. None of above.

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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd865b9b808190a1e8c283ba28d645 completed March 20, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69bd845f41f88190b75b8b64b9e41862 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:02 p.m.