Triple

T575875
Position Surface form Disambiguated ID Type / Status
Subject Chromium E13759 entity
Predicate supportsStandard P1587 FINISHED
Object ECMAScript E24470 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: ECMAScript | Statement: [Chromium, supportsStandard, ECMAScript]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ECMAScript
Context triple: [Chromium, supportsStandard, ECMAScript]
  • A. ECMAScript chosen
    ECMAScript is the official scripting language specification that defines the core features and behavior implemented by JavaScript and related languages.
  • B. JavaScript
    JavaScript is a high-level, dynamic programming language primarily used to create interactive and dynamic content on web pages.
  • C. ECMA-334
    ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
  • D. ECMA International
    ECMA International is a standards organization best known for maintaining the ECMAScript specification that underpins the JavaScript programming language.
  • E. JavaScriptCore
    JavaScriptCore is Apple’s high-performance JavaScript engine used primarily in the Safari web browser and WebKit-based applications.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b67395c8190a8046ff7debe9d1f completed March 1, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69a501bfb6408190bf7e1f462f39723d completed March 2, 2026, 3:19 a.m.
Created at: March 1, 2026, 7:33 p.m.