Triple
T5996677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Norton |
E133487
|
entity |
| Predicate | fieldOfWork |
P3
|
FINISHED |
| Object | MS-DOS |
E7153
|
NE 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: MS-DOS | Statement: [Peter Norton, fieldOfWork, MS-DOS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MS-DOS Context triple: [Peter Norton, fieldOfWork, MS-DOS]
-
A.
MS-DOS
chosen
MS-DOS is a command-line operating system that became the foundational software platform for early IBM-compatible personal computers in the 1980s and early 1990s.
-
B.
MS-DOS Executive
MS-DOS Executive is the simple file management and program-launching shell that served as the primary user interface in early versions of Microsoft Windows, notably Windows 1.0.
-
C.
DOS
DOS is the commonly used acronym for the United States Department of State, the federal executive department responsible for U.S. foreign policy and international relations.
-
D.
DR-DOS
DR-DOS is a DOS-compatible operating system developed by Digital Research as an alternative to MS-DOS, known for its advanced memory management and multitasking features for IBM PC-compatible computers.
-
E.
DOS/VS
DOS/VS is an IBM mainframe operating system variant designed for virtual storage support on the System/370 family.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e963f3c819082dd755e328ab947 |
completed | March 22, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c10876d4d0819083ac7431c8abaedd |
completed | March 23, 2026, 9:31 a.m. |
Created at: March 22, 2026, 4:05 p.m.