Triple
T38404068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiga 600 |
E900974
|
entity |
| Predicate | chipRAM |
P9335
|
FINISHED |
| Object | 1 MB standard |
—
|
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: 1 MB standard | Statement: [Amiga 600, chipRAM, 1 MB standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chipRAM Context triple: [Amiga 600, chipRAM, 1 MB standard]
-
A.
memoryController
Indicates a relationship where one entity manages, coordinates, or regulates access to memory resources for another entity or system.
-
B.
ramSpeed
Indicates the rate or velocity at which one entity forcefully collides with or rams into another.
-
C.
integratedMemoryController
Indicates that a memory controller is built directly into another component (such as a processor or chipset) rather than existing as a separate, external unit.
-
D.
hasRAM
chosen
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
E.
expandableRAM
Indicates that a device’s RAM can be increased beyond its original capacity, typically by adding or upgrading memory modules.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.