Triple
T27581757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM code page 437 |
E699601
|
entity |
| Predicate | oemCodePageFor |
P152053
|
FINISHED |
| Object | MS-DOS |
—
|
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: MS-DOS | Statement: [IBM code page 437, oemCodePageFor, MS-DOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oemCodePageFor Context triple: [IBM code page 437, oemCodePageFor, MS-DOS]
-
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.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
D.
BOMCodeUnit
Indicates a relationship where a bill of materials (BOM) is associated with a specific code unit that defines or implements its structure, logic, or processing.
-
E.
codingSystemContext
Indicates the coding system or classification framework within which a given code, identifier, or value is defined and interpreted.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63016cc1481908862c906df769a43 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:03 p.m.