Triple
T1775276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Air (M1, 2020) |
E38962
|
entity |
| Predicate | maxStorage |
P14460
|
FINISHED |
| Object | 2 TB SSD |
—
|
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: 2 TB SSD | Statement: [MacBook Air (M1, 2020), maxStorage, 2 TB SSD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxStorage Context triple: [MacBook Air (M1, 2020), maxStorage, 2 TB SSD]
-
A.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
B.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
C.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
D.
maximumDraft
Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
-
E.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.