Triple
T26377247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCS-4 |
E660932
|
entity |
| Predicate | maxROMChipsSupported |
P153296
|
FINISHED |
| Object | 16 Intel 4001 ROMs |
—
|
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: 16 Intel 4001 ROMs | Statement: [MCS-4, maxROMChipsSupported, 16 Intel 4001 ROMs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxROMChipsSupported Context triple: [MCS-4, maxROMChipsSupported, 16 Intel 4001 ROMs]
-
A.
supportsROMBlocks
chosen
Indicates that one entity provides compatibility with or the capability to use ROM (Read-Only Memory) blocks associated with another entity.
-
B.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an entity.
-
C.
hasROM
Indicates that an entity possesses or is equipped with a specific amount or type of Read-Only Memory (ROM).
-
D.
numberOfOfficialGamesSupported
Indicates the total count of official games that are supported in the specified context or system.
-
E.
maxRAMUnofficial
Indicates the maximum amount of RAM that can be used or installed in an unofficial or unsupported configuration.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61070d7348190ac0ac38a0249d2b8 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:02 p.m.