Triple
T20165854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Famicom Disk System |
E491822
|
entity |
| Predicate | totalDataCapacity |
P87535
|
FINISHED |
| Object | approximately 128 kilobytes per disk |
—
|
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: approximately 128 kilobytes per disk | Statement: [Famicom Disk System, totalDataCapacity, approximately 128 kilobytes per disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalDataCapacity Context triple: [Famicom Disk System, totalDataCapacity, approximately 128 kilobytes per disk]
-
A.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
-
B.
dataCapacity
chosen
Indicates the maximum amount of data that something can store, handle, or transmit.
-
C.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
-
D.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.