Triple

T18750132
Position Surface form Disambiguated ID Type / Status
Subject HLS E458504 entity
Predicate usedIn P98 FINISHED
Object ISO 20000-1 NE NERFINISHED

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 20000-1 | Statement: [HLS, usedIn, ISO 20000-1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 20000-1
Context triple: [HLS, usedIn, ISO 20000-1]
  • A. ISO/IEC 20000 chosen
    ISO/IEC 20000 is an international standard that specifies requirements for establishing, implementing, maintaining, and continually improving an IT service management system.
  • B. ISO/IEC 20000-11
    ISO/IEC 20000-11 is a part of the ISO/IEC 20000 family that provides guidance on the application and interpretation of the IT service management requirements defined in the core standard.
  • C. ISO/IEC 20000-10
    ISO/IEC 20000-10 is a part of the ISO/IEC 20000 family that provides guidance and terminology to support the implementation and understanding of IT service management standards.
  • D. ISO/IEC 20000-12
    ISO/IEC 20000-12 is a part of the ISO/IEC 20000 family that provides specific guidance supporting the implementation and interpretation of the IT service management standard.
  • E. ISO/IEC 20000-7
    ISO/IEC 20000-7 is a part of the ISO/IEC 20000 family of international standards that provides specific guidance related to IT service management practices.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e579ec71cc8190bb6d3fa6cca6dc8c completed April 20, 2026, 12:57 a.m.
Created at: April 10, 2026, 11:51 a.m.