Triple
T1718665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 95 |
E37343
|
entity |
| Predicate | systemRequirements |
P29568
|
FINISHED |
| Object | 80386DX CPU or higher |
—
|
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: 80386DX CPU or higher | Statement: [Windows 95, systemRequirements, 80386DX CPU or higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemRequirements Context triple: [Windows 95, systemRequirements, 80386DX CPU or higher]
-
A.
platformRequirement
chosen
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
B.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
C.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.