Triple
T9945805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | File Allocation Table |
E195199
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
ECMA-107
ECMA-107 is an ECMA standard that defines the File Allocation Table (FAT) file system format and related conventions for data storage on computer media.
|
E830122
|
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-107 | Statement: [File Allocation Table, standardizedIn, ECMA-107]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-107 Context triple: [File Allocation Table, standardizedIn, ECMA-107]
-
A.
ECMA-372
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
-
B.
ECMA-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
-
C.
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.
-
D.
ECMA-334
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
E.
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.
- 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-107 Triple: [File Allocation Table, standardizedIn, ECMA-107]
Generated description
ECMA-107 is an ECMA standard that defines the File Allocation Table (FAT) file system format and related conventions for data storage on computer media.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ECMA-107 Target entity description: ECMA-107 is an ECMA standard that defines the File Allocation Table (FAT) file system format and related conventions for data storage on computer media.
-
A.
ECMA-372
ECMA-372 is the ECMA standard that defines the C++/CLI language specification for managed extensions of C++ targeting the .NET runtime.
-
B.
ECMA-367
ECMA-367 is the official international standard that defines the syntax and semantics of the Eiffel programming language.
-
C.
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.
-
D.
ECMA-334
ECMA-334 is the ECMA International standard that formally defines the C# programming language specification.
-
E.
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.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb655fba0819084a1e757b68c25d4 |
completed | April 2, 2026, 12:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2292257bc8190b3a15de60d7c9ba2 |
completed | April 5, 2026, 9:19 a.m. |
| NEDg | Description generation | batch_69d229b3b200819083aa90f64eaec9e8 |
completed | April 5, 2026, 9:21 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d22a2d14fc8190b2493ce571811d43 |
completed | April 5, 2026, 9:23 a.m. |
Created at: March 30, 2026, 8:45 p.m.