Triple
T8520977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola Droid |
E201691
|
entity |
| Predicate | expandableStorageMax |
P52985
|
FINISHED |
| Object | 32 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: 32 GB | Statement: [Motorola Droid, expandableStorageMax, 32 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandableStorageMax Context triple: [Motorola Droid, expandableStorageMax, 32 GB]
-
A.
expandableCapacity
Indicates that an entity’s capacity can be increased beyond its initial or default level, typically through additional resources, components, or configuration.
-
B.
expandableRAM
Indicates that a device’s RAM can be increased beyond its original capacity, typically by adding or upgrading memory modules.
-
C.
storageCapacity
chosen
Indicates the maximum amount of data or material that a storage entity can hold.
-
D.
expandedCapacity
Indicates that an entity’s capacity has been increased beyond its previous or standard level.
-
E.
ramExpandableTo
Indicates that a device’s RAM can be increased from its current capacity up to a specified maximum amount.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.