Triple
T21749709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinclair BASIC |
E536880
|
entity |
| Predicate | typicalROMSize |
P18083
|
FINISHED |
| Object | 8 KB (ZX80/ZX81 versions) |
—
|
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: 8 KB (ZX80/ZX81 versions) | Statement: [Sinclair BASIC, typicalROMSize, 8 KB (ZX80/ZX81 versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalROMSize Context triple: [Sinclair BASIC, typicalROMSize, 8 KB (ZX80/ZX81 versions)]
-
A.
flashSizeMB
Indicates the amount of flash memory associated with an entity, measured in megabytes (MB).
-
B.
hasROM
Indicates that an entity possesses or is equipped with a specific amount or type of Read-Only Memory (ROM).
-
C.
romSize
chosen
Indicates the amount of read-only memory (ROM) associated with an entity, typically measured as its storage capacity.
-
D.
mainMemorySize
Indicates the relationship specifying the size or capacity of an entity's main memory.
-
E.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a78bd908190b74e26ab1cc8788f |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.