Triple
T1696122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC XT |
E36661
|
entity |
| Predicate | maximumRam |
P9335
|
FINISHED |
| Object | 640 KB |
—
|
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: 640 KB | Statement: [IBM PC XT, maximumRam, 640 KB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRam Context triple: [IBM PC XT, maximumRam, 640 KB]
-
A.
minRAM
Indicates that an entity requires at least a specified minimum amount of RAM to function or be considered valid.
-
B.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
C.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
hasRAM
chosen
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
E.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.