Triple
T33027311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBCDIC |
E845075
|
entity |
| Predicate | usesCodePages |
P152053
|
FINISHED |
| Object | IBM code pages |
—
|
LITERAL 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: IBM code pages | Statement: [EBCDIC, usesCodePages, IBM code pages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodePages Context triple: [EBCDIC, usesCodePages, IBM code pages]
-
A.
usesCodePageLayout
Indicates that one entity arranges or interprets character data according to the code page layout defined or provided by another entity.
-
B.
hasCodePageRelationship
chosen
Indicates a relationship where one entity is associated with, linked to, or defined in terms of a specific code page or character encoding scheme.
-
C.
usesCodePoints
Indicates that one entity represents, encodes, or operates using the specific set of Unicode code points defined by another entity.
-
D.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
E.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
- F. None of above.
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:23 a.m.