classic Mac OS Code Fragment Manager
E864393
The classic Mac OS Code Fragment Manager was a system component responsible for loading, linking, and managing shared libraries and code fragments in pre-OS X versions of the Macintosh operating system.
All labels observed (1)
| Label | Occurrences |
|---|---|
| classic Mac OS Code Fragment Manager canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10456486 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: classic Mac OS Code Fragment Manager Context triple: [dyld, replaces, classic Mac OS Code Fragment Manager]
-
A.
Macintosh Toolbox
The Macintosh Toolbox was the core collection of system software routines and services that provided the graphical user interface, event handling, and application support framework for the classic Mac OS.
-
B.
Macintosh SCSI Manager
Macintosh SCSI Manager is the classic Mac OS software subsystem that provides low-level control and communication with SCSI storage and peripheral devices on 68k-based Macintosh computers.
-
C.
MacQuinn
MacQuinn is a surname variant of Quinn, typically associated with Irish or Gaelic heritage.
-
D.
NeXTSTEP Interface Builder
NeXTSTEP Interface Builder was a pioneering graphical tool for visually designing user interfaces and connecting them to application code in the NeXTSTEP operating system.
-
E.
NeXTSTEP Foundation Kit
NeXTSTEP Foundation Kit is an object-oriented application framework developed by NeXT Inc. that provided core classes and services for building NeXTSTEP applications and later influenced Apple’s Cocoa frameworks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: classic Mac OS Code Fragment Manager Target entity description: The classic Mac OS Code Fragment Manager was a system component responsible for loading, linking, and managing shared libraries and code fragments in pre-OS X versions of the Macintosh operating system.
-
A.
Macintosh Toolbox
The Macintosh Toolbox was the core collection of system software routines and services that provided the graphical user interface, event handling, and application support framework for the classic Mac OS.
-
B.
Macintosh SCSI Manager
Macintosh SCSI Manager is the classic Mac OS software subsystem that provides low-level control and communication with SCSI storage and peripheral devices on 68k-based Macintosh computers.
-
C.
MacQuinn
MacQuinn is a surname variant of Quinn, typically associated with Irish or Gaelic heritage.
-
D.
NeXTSTEP Interface Builder
NeXTSTEP Interface Builder was a pioneering graphical tool for visually designing user interfaces and connecting them to application code in the NeXTSTEP operating system.
-
E.
NeXTSTEP Foundation Kit
NeXTSTEP Foundation Kit is an object-oriented application framework developed by NeXT Inc. that provided core classes and services for building NeXTSTEP applications and later influenced Apple’s Cocoa frameworks.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
dynamic linker
ⓘ
runtime loader ⓘ system component ⓘ |
| alsoSupportsArchitecture | Motorola 680x0 NERFINISHED ⓘ |
| category | Mac OS system software ⓘ |
| developer | Apple Computer, Inc. NERFINISHED ⓘ |
| documentation |
Apple Developer Documentation for CFM
NERFINISHED
ⓘ
Inside Macintosh: PowerPC System Software NERFINISHED ⓘ |
| era | pre-Mac OS X ⓘ |
| exposesAPI | CFM programming interface ⓘ |
| goal |
enable dynamic loading of libraries
ⓘ
support modular, shared code ⓘ |
| handles |
fragment loading from disk
ⓘ
fragment reference counting ⓘ fragment unloading ⓘ |
| introducedFor | PowerPC transition on classic Mac OS ⓘ |
| manages |
fragment global state
ⓘ
fragment initialization order ⓘ |
| operatingSystem | Classic Mac OS NERFINISHED ⓘ |
| partOf | Mac OS runtime environment NERFINISHED ⓘ |
| primaryArchitecture | PowerPC NERFINISHED ⓘ |
| provides |
initialization of code fragments
ⓘ
relocation of code fragments ⓘ runtime linking services ⓘ symbol resolution ⓘ termination of code fragments ⓘ |
| relatedTo |
CodeWarrior
NERFINISHED
ⓘ
PowerPC Runtime Architecture NERFINISHED ⓘ |
| replacedBy |
Mac OS X dyld
NERFINISHED
ⓘ
Mach-O dynamic linker NERFINISHED ⓘ |
| responsibleFor |
linking code fragments
ⓘ
loading code fragments ⓘ managing code fragments at runtime ⓘ managing shared libraries ⓘ |
| supports |
68k code fragments
ⓘ
PowerPC code fragments ⓘ dynamically loaded code ⓘ shared libraries ⓘ |
| supportsConcept |
code fragment
ⓘ
exported symbols ⓘ fragment connection ⓘ import library ⓘ |
| usedBy |
classic Mac OS applications
ⓘ
shared libraries on classic Mac OS ⓘ |
| usesFileFormat |
CFM shared library format
NERFINISHED
ⓘ
Code Fragment Manager container format NERFINISHED ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: classic Mac OS Code Fragment Manager Description of subject: The classic Mac OS Code Fragment Manager was a system component responsible for loading, linking, and managing shared libraries and code fragments in pre-OS X versions of the Macintosh operating system.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.