Triple
T1768034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface Laptop |
E38808
|
entity |
| Predicate | typicalStorageType |
P8611
|
FINISHED |
| Object | 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: SSD | Statement: [Surface Laptop, typicalStorageType, SSD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStorageType Context triple: [Surface Laptop, typicalStorageType, SSD]
-
A.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
B.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
D.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
-
E.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification 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_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.