Triple
T23387637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-7 |
E593926
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | ECMA-118 |
—
|
NE NERFINISHED |
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-118 | Statement: [ISO/IEC 8859-7, basedOn, ECMA-118]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECMA-118 Context triple: [ISO/IEC 8859-7, basedOn, ECMA-118]
-
A.
ECMA-118
chosen
ECMA-118 is a character encoding standard for the Greek alphabet that corresponds to the ISO/IEC 8859-7 code page.
-
B.
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.
-
C.
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.
-
D.
ECMA-404
ECMA-404 is the ECMA International standard that formally defines the JSON (JavaScript Object Notation) data interchange format.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 17, 2026, 5:35 p.m.