Triple
T2105910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC AT |
E37193
|
entity |
| Predicate | standardHardDisk |
P16222
|
FINISHED |
| Object | 20 MB hard disk drive |
—
|
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: 20 MB hard disk drive | Statement: [IBM PC AT, standardHardDisk, 20 MB hard disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardHardDisk Context triple: [IBM PC AT, standardHardDisk, 20 MB hard disk drive]
-
A.
hasInternalHardDrive
chosen
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
B.
standardDiscDiameter
Indicates that one entity specifies the standard diameter measurement of a disc associated with another entity.
-
C.
floppyDriveCapacity
Indicates the storage capacity associated with a floppy drive.
-
D.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
E.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbaddeb148190b728bce7a7b041fb |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.