Triple

T18770598
Position Surface form Disambiguated ID Type / Status
Subject ECMA standard E459007 entity
Predicate hasExample P1259 FINISHED
Object ECMA-335 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: ECMA-335 | Statement: [ECMA standard, hasExample, ECMA-335]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ECMA-335
Context triple: [ECMA standard, hasExample, ECMA-335]
  • A. ECMA-335 chosen
    ECMA-335 is the international standard that defines the Common Language Infrastructure (CLI), including the core runtime, type system, and metadata used by .NET languages.
  • B. ECMA-376
    ECMA-376 is the ECMA International standard that defines the Office Open XML file formats used by Microsoft Office and other productivity applications.
  • C. Microsoft Intermediate Language
    Microsoft Intermediate Language is the low-level, platform-independent bytecode used by the .NET Framework’s Common Language Runtime as the compilation target for .NET languages before just-in-time compilation to native machine code.
  • D. ECMA-334
    ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
  • E. Common Language Runtime
    The Common Language Runtime is the virtual machine component of Microsoft's .NET platform that manages code execution, memory, security, and other runtime services for .NET applications.
  • 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e59335a01881908731371be1e27a6b completed April 20, 2026, 2:45 a.m.
Created at: April 10, 2026, 11:52 a.m.