Triple
T8414537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac 68k bootloaders |
E198700
|
entity |
| Predicate | bootSourceSelection |
P31985
|
FINISHED |
| Object | internal disk |
—
|
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: internal disk | Statement: [Mac 68k bootloaders, bootSourceSelection, internal disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootSourceSelection Context triple: [Mac 68k bootloaders, bootSourceSelection, internal disk]
-
A.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
-
B.
bootCatalogLocation
Indicates the location or source from which a boot catalog (e.g., for system or media boot configuration) is stored or accessed.
-
C.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
D.
bootLoader
Indicates that one entity functions as the boot loader responsible for initializing or starting up another entity (such as a system, device, or software environment).
-
E.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset state.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e328cc8190b3b038005d0bb66f |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.