Triple
T9502675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Pro 15-inch (2019) |
E229181
|
entity |
| Predicate | storageCapacityMin |
P41028
|
FINISHED |
| Object | 256 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: 256 GB | Statement: [MacBook Pro 15-inch (2019), storageCapacityMin, 256 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCapacityMin Context triple: [MacBook Pro 15-inch (2019), storageCapacityMin, 256 GB]
-
A.
minStorageCapacity
chosen
Indicates the minimum storage capacity required, allowed, or guaranteed in a given context or relationship.
-
B.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
C.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
D.
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.
-
E.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983ea6048190a2d7924c8e6d1fbc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.