Triple
T33027282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBCDIC |
E845075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IBM character encoding |
C1329
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: IBM character encoding Context triple: [EBCDIC, instanceOf, IBM character encoding]
-
A.
IBM PC character set
The IBM PC character set is an extended 8-bit encoding used on early IBM PCs that includes standard ASCII characters plus additional graphical, line-drawing, and international symbols for text-based user interfaces.
-
B.
character encoding standard
chosen
A character encoding standard is a defined system that maps characters from a writing system to numeric codes so they can be stored, processed, and transmitted by computers.
-
C.
ISO standard code set
A standardized collection of internationally recognized codes defined by the International Organization for Standardization (ISO) to uniquely and consistently represent specific types of data, such as countries, currencies, languages, or measurements.
-
D.
Unicode standard
The Unicode standard is a universal character encoding system that assigns a unique code point to virtually every written symbol, enabling consistent text representation and processing across different platforms, languages, and devices.
-
E.
IBM 3270 family device
An IBM 3270 family device is a block-oriented terminal or controller used to interact with mainframe systems, optimized for high-speed, low-overhead data entry and display in enterprise environments.
- F. None of above.
Provenance (1 batch)
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.