Triple
T28972046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFF-8639 |
E734298
|
entity |
| Predicate | supportsDriveType |
P203861
|
FINISHED |
| Object | enterprise NVMe 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: enterprise NVMe SSD | Statement: [SFF-8639, supportsDriveType, enterprise NVMe SSD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDriveType Context triple: [SFF-8639, supportsDriveType, enterprise NVMe SSD]
-
A.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
C.
supportsDriverType
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
D.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
E.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
- F. None of above. chosen
Provenance (4 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0227ce59a081909fe1ba1181d86b4d |
completed | May 11, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_6a02273989208190beb948b8c7bdaee3 |
completed | May 11, 2026, 7 p.m. |
| PDg | Predicate description generation | batch_6a0227cd6e348190983e90e349aa155b |
completed | May 11, 2026, 7:02 p.m. |
Created at: April 28, 2026, 9:06 a.m.