Triple
T10826448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mono project |
E255508
|
entity |
| Predicate | implementsStandard |
P1587
|
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: [Mono project, implementsStandard, ECMA-334]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-334 Context triple: [Mono project, implementsStandard, ECMA-334]
-
A.
ECMA-334
chosen
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
B.
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.
-
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-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
-
E.
Ecma TC45
Ecma TC45 is the Ecma International technical committee responsible for standardizing and evolving the Office Open XML document formats.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d1c24881909f56d56207cccbef |
completed | April 9, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de858672d8819094baf4fe98b8dea4 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.