Triple
T15616101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa File System |
E375415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proprietary file system |
C36414
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: proprietary file system Context triple: [Lisa File System, instanceOf, proprietary file system]
-
A.
proprietary file format
A proprietary file format is a data storage structure whose specifications are owned and controlled by an individual or organization, often restricting interoperability and requiring specific software to access or modify its contents.
-
B.
proprietary codec
A proprietary codec is a closed, privately owned method for encoding and decoding digital data (such as audio or video) that typically requires licensing or permission to use.
-
C.
FAT file system variant
A FAT file system variant is a specific implementation or extension of the File Allocation Table architecture that defines how data is organized, stored, and managed on storage media, often differing in cluster size limits, maximum volume and file sizes, and supported features.
-
D.
proprietary governor
A proprietary governor is a colonial-era official or authority figure granted governing powers over a territory by a private owner or chartered company rather than directly by a sovereign state.
-
E.
Unix-like file system
A Unix-like file system is a hierarchical, tree-structured organization of files and directories that provides standardized interfaces and semantics for storing, accessing, and managing data on Unix and Unix-inspired operating systems.
- F. None of above. chosen
Provenance (1 batch)
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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:13 a.m.