Triple
T562904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh 128K |
E13491
|
entity |
| Predicate | floppyDriveCapacity |
P16219
|
FINISHED |
| Object | 400 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: 400 KB | Statement: [Macintosh 128K, floppyDriveCapacity, 400 KB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floppyDriveCapacity Context triple: [Macintosh 128K, floppyDriveCapacity, 400 KB]
-
A.
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.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
isTypicallyFilledWith
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
-
D.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
E.
batteryCapacity
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
- F. None of above. chosen
Provenance (4 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498ff0c0081908947376a38b10d72 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:32 p.m.