Triple
T6033671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Open XML (ECMA-376) |
E134365
|
entity |
| Predicate | maintainedBy |
P86
|
FINISHED |
| Object |
Ecma TC45
Ecma TC45 is the Ecma International technical committee responsible for standardizing and evolving the Office Open XML document formats.
|
E565030
|
NE FINISHED |
How this triple was built (4 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 TC45 | Statement: [Office Open XML (ECMA-376), maintainedBy, Ecma TC45]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ecma TC45 Context triple: [Office Open XML (ECMA-376), maintainedBy, Ecma TC45]
-
A.
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.
-
B.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
-
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-334
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
E.
ECMA-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ecma TC45 Triple: [Office Open XML (ECMA-376), maintainedBy, Ecma TC45]
Generated description
Ecma TC45 is the Ecma International technical committee responsible for standardizing and evolving the Office Open XML document formats.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ecma TC45 Target entity description: Ecma TC45 is the Ecma International technical committee responsible for standardizing and evolving the Office Open XML document formats.
-
A.
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.
-
B.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
-
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-334
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
E.
ECMA-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
- F. None of above. chosen
Provenance (5 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_69c11388aec881908408d5844c96ea2d |
completed | March 23, 2026, 10:18 a.m. |
| NEDg | Description generation | batch_69c11689c0788190847435b526572edc |
completed | March 23, 2026, 10:31 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c116eb349c81908cad0bf5ccc458bc |
completed | March 23, 2026, 10:33 a.m. |
Created at: March 22, 2026, 4:08 p.m.