Triple
T2977574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSMAC ELF |
E80434
|
entity |
| Predicate | initialMemorySize |
P28148
|
FINISHED |
| Object | 256 bytes |
—
|
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: 256 bytes | Statement: [COSMAC ELF, initialMemorySize, 256 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialMemorySize Context triple: [COSMAC ELF, initialMemorySize, 256 bytes]
-
A.
initialHardDriveCapacity
Indicates the original storage capacity of a hard drive at the time it was first provided, installed, or configured.
-
B.
minRAM
Indicates that an entity requires at least a specified minimum amount of RAM to function or be considered valid.
-
C.
primaryMemoryType
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
D.
originalCapacity
chosen
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
E.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.