Triple
T2793116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU Parted |
E61972
|
entity |
| Predicate | supportsStorageDevice |
P31893
|
FINISHED |
| Object | hard disk 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: hard disk drive | Statement: [GNU Parted, supportsStorageDevice, hard disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStorageDevice Context triple: [GNU Parted, supportsStorageDevice, hard disk drive]
-
A.
supportsExternalDrive
Indicates that one entity is capable of working with, recognizing, or providing functionality for an external storage drive.
-
B.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
C.
supportsMemoryCard
Indicates that one entity is compatible with and can accept or use a memory card associated with another entity.
-
D.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
E.
supportsInstallationMedia
chosen
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.