Triple

T1612357
Position Surface form Disambiguated ID Type / Status
Subject C++/CLI E34640 entity
Predicate ECMANumber P508 FINISHED
Object ECMA-372
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
E185508 NE FINISHED

How this triple was built (5 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-372 | Statement: [C++/CLI, ECMANumber, ECMA-372]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ECMA-372
Context triple: [C++/CLI, ECMANumber, ECMA-372]
  • A. ECMA-334
    ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
  • B. ECMA-119
    ECMA-119 is an ECMA standard that defines the file system format for CD-ROMs, serving as the basis for the ISO 9660 standard.
  • C. ECMAScript
    ECMAScript is the official scripting language specification that defines the core features and behavior implemented by JavaScript and related languages.
  • D. ECMA-404
    ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
  • E. 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.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ECMA-372
Triple: [C++/CLI, ECMANumber, ECMA-372]
Generated description
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: ECMA-372
Target entity description: ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
  • A. ECMA-334
    ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
  • B. ECMA-119
    ECMA-119 is an ECMA standard that defines the file system format for CD-ROMs, serving as the basis for the ISO 9660 standard.
  • C. ECMAScript
    ECMAScript is the official scripting language specification that defines the core features and behavior implemented by JavaScript and related languages.
  • D. ECMA-404
    ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
  • E. 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.
  • F. None of above. chosen
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ECMANumber
Context triple: [C++/CLI, ECMANumber, ECMA-372]
  • A. eraCode
    Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
  • B. numericCode chosen
    Indicates that an entity is associated with a specific numerical identifier or classification code.
  • C. evaCount
    Indicates a relationship where a specific count or number is associated with an evaluation-related event, action, or occurrence.
  • D. eraNumberInJapan
    Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
  • E. SSNumber
    Indicates that an entity has a specific Social Security Number assigned to it.
  • F. None of above.

Provenance (6 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a93fa6926081908bc78d15c0be3185 completed March 5, 2026, 8:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad60903f94819095dc90d6ce959017 completed March 8, 2026, 11:42 a.m.
NEDg Description generation batch_69ad6148d5ac819096ee1a3e97331ed2 completed March 8, 2026, 11:45 a.m.
NED2 Entity disambiguation (via description) batch_69ad62028a448190a0c3f0dadae6a741 completed March 8, 2026, 11:48 a.m.
PD Predicate disambiguation batch_69a907c35f848190a2428c52e81d013e completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:28 p.m.