Triple
T122851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chromebook |
E2484
|
entity |
| Predicate | typicalLocalStorage |
P751
|
FINISHED |
| Object | solid-state drive |
—
|
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: solid-state drive | Statement: [Chromebook, typicalLocalStorage, solid-state drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocalStorage Context triple: [Chromebook, typicalLocalStorage, solid-state drive]
-
A.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
B.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
C.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
D.
standardType
chosen
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
typicalFields
Indicates the standard or commonly occurring attributes or data fields that are usually associated with an entity or record.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a2573b4e7481909ee09d2899f8a74b |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.