Triple
T23387623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-7 |
E593926
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object |
ECMA-118
ECMA-118 is a character encoding standard for the Greek alphabet that corresponds to the ISO/IEC 8859-7 code page.
|
E1582268
|
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-118 | Statement: [ISO/IEC 8859-7, alsoKnownAs, ECMA-118]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-118 Context triple: [ISO/IEC 8859-7, alsoKnownAs, ECMA-118]
-
A.
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.
-
B.
ECMA-125
ECMA-125 is an ECMA standard that defines the physical and magnetic recording characteristics for 3.5-inch floppy disk media used in microcomputer systems.
-
C.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
-
D.
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.
-
E.
ECMA-35
ECMA-35 is a character encoding standard developed by Ecma International that defines 8-bit coded character sets and control functions for information interchange, closely aligned with ISO/IEC 2022 mechanisms.
- 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-118 Triple: [ISO/IEC 8859-7, alsoKnownAs, ECMA-118]
Generated description
ECMA-118 is a character encoding standard for the Greek alphabet that corresponds to the ISO/IEC 8859-7 code page.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ECMA-118 Target entity description: ECMA-118 is a character encoding standard for the Greek alphabet that corresponds to the ISO/IEC 8859-7 code page.
-
A.
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.
-
B.
ECMA-125
ECMA-125 is an ECMA standard that defines the physical and magnetic recording characteristics for 3.5-inch floppy disk media used in microcomputer systems.
-
C.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
-
D.
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.
-
E.
ECMA-35
ECMA-35 is a character encoding standard developed by Ecma International that defines 8-bit coded character sets and control functions for information interchange, closely aligned with ISO/IEC 2022 mechanisms.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c5de999488190be021920241b7f25 |
completed | May 19, 2026, 12:56 p.m. |
| NEDg | Description generation | batch_6a0c5e7eb7b481908b3cece1823cf785 |
completed | May 19, 2026, 12:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0c5eef81e48190b62da26fb8d65223 |
completed | May 19, 2026, 1 p.m. |
Created at: April 17, 2026, 5:35 p.m.