Triple
T1612621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECMA-334 |
E34645
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | ISO/IEC 23270 |
E34646
|
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: ISO/IEC 23270 | Statement: [ECMA-334, relatedStandard, ISO/IEC 23270]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 23270 Context triple: [ECMA-334, relatedStandard, ISO/IEC 23270]
-
A.
ISO/IEC 23270
chosen
ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
-
B.
ISO/IEC 23271
ISO/IEC 23271 is the international standard that defines the Common Language Infrastructure (CLI), the core runtime and execution environment underlying technologies like Microsoft .NET.
-
C.
ISO/IEC 23273
ISO/IEC 23273 is an international standard that specifies safety requirements for hydrogen-fueled road vehicles, particularly focusing on fuel cell vehicle safety.
-
D.
ISO/IEC 23272
ISO/IEC 23272 is an international standard in the joint ISO/IEC series that specifies technical requirements and guidelines in the field of information and communication technologies.
-
E.
ISO/IEC 30170
ISO/IEC 30170 is an international standard that formally specifies the Ruby programming language.
- 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_69ad8ab5e8b88190b95af87391e5bb16 |
completed | March 8, 2026, 2:41 p.m. |
Created at: March 4, 2026, 7:28 p.m.