Triple
T23423965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Norton's DOS Guide |
E560739
|
entity |
| Predicate | operatingSystemCovered |
P82544
|
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: [Peter Norton's DOS Guide, operatingSystemCovered, MS-DOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingSystemCovered Context triple: [Peter Norton's DOS Guide, operatingSystemCovered, MS-DOS]
-
A.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
B.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
C.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
D.
operatorSystem
Indicates a relationship where one entity functions as the operating system that manages or controls another entity (such as a device, application, or system).
-
E.
relatedOperatingSystem
chosen
Indicates that there is an association between an entity and an operating system that is relevant to its use, compatibility, or operation.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54838fc8190a3205ca72daaf107 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.