Triple

T1166084
Position Surface form Disambiguated ID Type / Status
Subject ECMA International E24801 entity
Predicate TC39ResponsibleFor P636 FINISHED
Object ECMAScript standardization LITERAL 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: ECMAScript standardization | Statement: [ECMA International, TC39ResponsibleFor, ECMAScript standardization]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: TC39ResponsibleFor
Context triple: [ECMA International, TC39ResponsibleFor, ECMAScript standardization]
  • A. responsibleFor chosen
    Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
  • B. onStandardsTrack
    Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
  • C. aimedToImplement
    Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
  • D. hasTechnicalCommittee
    Indicates that an entity is associated with or overseen by a specific technical committee.
  • E. normativeFor
    Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
  • F. None of above.

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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bccc62a88190882d8801908015a4 completed March 1, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69a4bb548c1481909092626c572d8782 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.