Triple

T1631957
Position Surface form Disambiguated ID Type / Status
Subject ISO 7498 E35275 entity
Predicate relatedTo P37 FINISHED
Object ISO 7498-2 E35275 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 7498-2 | Statement: [ISO 7498, relatedTo, ISO 7498-2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 7498-2
Context triple: [ISO 7498, relatedTo, ISO 7498-2]
  • A. ISO 7498 chosen
    ISO 7498 is the international standard that defines the Open Systems Interconnection (OSI) reference model for network communications.
  • B. ISO/IEC 8652
    ISO/IEC 8652 is the international standard that formally defines the Ada programming language, including its syntax, semantics, and core features.
  • C. ISO/IEC 23271
    ISO/IEC 23271 is the international standard that defines the Common Language Infrastructure (CLI), the core runtime and execution environment underlying technologies like Microsoft .NET.
  • D. ISO/IEC 23270
    ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
  • E. 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.
  • 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_69a886036bc081909ff5de16dbe5e8ea completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a909f6ee1881908f0753a77a2c4665 completed March 5, 2026, 4:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad6096584c81909ce50469f23a8a12 completed March 8, 2026, 11:42 a.m.
Created at: March 4, 2026, 7:28 p.m.