Triple
T9187996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmigaDOS |
E220505
|
entity |
| Predicate | typicalBootScript |
P28573
|
FINISHED |
| Object | S:Startup-Sequence |
—
|
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: S:Startup-Sequence | Statement: [AmigaDOS, typicalBootScript, S:Startup-Sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBootScript Context triple: [AmigaDOS, typicalBootScript, S:Startup-Sequence]
-
A.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset state.
-
B.
bootMedium
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
C.
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).
-
D.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
-
E.
typicalSetup
chosen
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31d91d48190b8b8874e09c84404 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.