Triple
T6033620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Open XML (ECMA-376) |
E134365
|
entity |
| Predicate | standardNumber |
P4626
|
FINISHED |
| Object | ECMA-376 |
E134364
|
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-376 | Statement: [Office Open XML (ECMA-376), standardNumber, ECMA-376]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-376 Context triple: [Office Open XML (ECMA-376), standardNumber, ECMA-376]
-
A.
ECMA-376
chosen
ECMA-376 is the ECMA International standard that defines the Office Open XML file formats used by Microsoft Office and other productivity applications.
-
B.
ECMA-335
ECMA-335 is the international standard that defines the Common Language Infrastructure (CLI), including the core runtime, type system, and metadata used by .NET languages.
-
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.
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-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_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.