Triple

T22812932
Position Surface form Disambiguated ID Type / Status
Subject Ecma TC45 E565030 entity
Predicate fullName P16 FINISHED
Object Ecma International Technical Committee 45 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 International Technical Committee 45 | Statement: [Ecma TC45, fullName, Ecma International Technical Committee 45]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ecma International Technical Committee 45
Context triple: [Ecma TC45, fullName, Ecma International Technical Committee 45]
  • A. Ecma TC45 chosen
    Ecma TC45 is the Ecma International technical committee responsible for standardizing and evolving the Office Open XML document formats.
  • B. ECMA International
    ECMA International is a standards organization best known for maintaining the ECMAScript specification that underpins the JavaScript programming language.
  • C. ECMA-404
    ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
  • D. ECMA-340
    ECMA-340 is an international standard that specifies the Near Field Communication (NFC) interface and protocol for short-range wireless communication between electronic devices.
  • E. ECMA-372
    ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
  • 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d61c6f081908d3911710b3aff51 completed April 29, 2026, 3:39 a.m.
Created at: April 17, 2026, 3:32 p.m.