Triple
T6033562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECMA-404 |
E134363
|
entity |
| Predicate | maintainedBy |
P86
|
FINISHED |
| Object | Ecma TC39 |
E134960
|
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: Ecma TC39 | Statement: [ECMA-404, maintainedBy, Ecma TC39]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ecma TC39 Context triple: [ECMA-404, maintainedBy, Ecma TC39]
-
A.
TC39
chosen
TC39 is the Ecma International committee responsible for developing and standardizing the ECMAScript language, which underpins JavaScript.
-
B.
ECMAScript
ECMAScript is the official scripting language specification that defines the core features and behavior implemented by JavaScript and related languages.
-
C.
ECMA standard
An ECMA standard is a technical specification published by Ecma International that defines interoperable formats, languages, or interfaces for information and communication systems.
-
D.
ECMA-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
-
E.
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.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113855ad08190b9ff826a2f39c356 |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:08 p.m.