Triple
T2585473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iMac G3 |
E57187
|
entity |
| Predicate | initialHardDriveCapacity |
P40530
|
FINISHED |
| Object | 4 GB |
—
|
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 GB | Statement: [iMac G3, initialHardDriveCapacity, 4 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialHardDriveCapacity Context triple: [iMac G3, initialHardDriveCapacity, 4 GB]
-
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.
floppyDriveCapacity
Indicates the storage capacity associated with a floppy drive.
-
C.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
originalCapacity
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
E.
dataCapacityDigits
Indicates the number of decimal digits used to represent or specify a data capacity value.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cd07588190b3cb8cc348f12938 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.