Triple
T1612665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 23270 |
E34646
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | ECMA-334 |
E34645
|
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-334 | Statement: [ISO/IEC 23270, relatedTo, ECMA-334]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-334 Context triple: [ISO/IEC 23270, relatedTo, ECMA-334]
-
A.
ECMA-334
chosen
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
B.
ECMA-372
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
-
C.
ECMA-119
ECMA-119 is an ECMA standard that defines the file system format for CD-ROMs, serving as the basis for the ISO 9660 standard.
-
D.
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.
-
E.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9098cd03081908c67f95fd54d2071 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad680e8c908190a62a0a2f92a2b335 |
completed | March 8, 2026, 12:14 p.m. |
Created at: March 4, 2026, 7:28 p.m.