Triple
T29010629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFP 3.1 |
E736556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apple Filing Protocol version |
C24439
|
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: Apple Filing Protocol version Context triple: [AFP 3.1, instanceOf, Apple Filing Protocol version]
-
A.
Macintosh file system
A Macintosh file system is a hierarchical structure used by classic Mac OS and macOS to organize, store, and manage files and directories on storage devices, supporting metadata, resource forks, and various file attributes.
-
B.
AppleTalk protocol
chosen
AppleTalk protocol is a discontinued suite of networking protocols developed by Apple for connecting Macintosh computers and devices in local area networks, providing services such as addressing, routing, and file/print sharing.
-
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.
FAT file system
A FAT file system is a simple, widely supported disk file system that organizes and manages files using a File Allocation Table to track the location and allocation status of data clusters on storage media.
-
E.
Mac OS X feature
A Mac OS X feature is a distinct capability or tool integrated into the Mac operating system that enhances user experience, productivity, or system functionality.
- F. None of above.
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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:42 a.m.