Triple
T2207454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presto |
E50833
|
entity |
| Predicate | supports |
P516
|
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: [Presto, supports, ECMAScript]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMAScript Context triple: [Presto, supports, 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.
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.
-
C.
ECMA-372
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
-
D.
JavaScript
JavaScript is a high-level, dynamic programming language primarily used to create interactive and dynamic content on web pages.
-
E.
ECMA-334
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfcbb83081908d5b2f1603c7b4d2 |
completed | March 7, 2026, 6:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae654b89b081908f8c8b9bfc0b6579 |
completed | March 9, 2026, 6:14 a.m. |
Created at: March 4, 2026, 7:46 p.m.