Triple
T25933549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMSAI 8080 |
E653490
|
entity |
| Predicate | typicalRAMConfiguration |
P9335
|
FINISHED |
| Object | 4 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: 4 KB | Statement: [IMSAI 8080, typicalRAMConfiguration, 4 KB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRAMConfiguration Context triple: [IMSAI 8080, typicalRAMConfiguration, 4 KB]
-
A.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an entity.
-
B.
typicalRAMRangeMB
Indicates the usual or expected range of RAM capacity, measured in megabytes, associated with an entity.
-
C.
memoryConfigurations
Indicates how memory resources are arranged, allocated, or structured within a system or component.
-
D.
typicalRAMExpansionSizes
Indicates the commonly used or standard memory capacity increments by which a system’s RAM can be expanded.
-
E.
hasRAM
chosen
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 22, 2026, 8:37 a.m.