Triple
T3636137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twiggy floppy drive |
E77070
|
entity |
| Predicate | bootDeviceFor |
P31985
|
FINISHED |
| Object | early Apple Lisa configurations |
—
|
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: early Apple Lisa configurations | Statement: [Twiggy floppy drive, bootDeviceFor, early Apple Lisa configurations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootDeviceFor Context triple: [Twiggy floppy drive, bootDeviceFor, early Apple Lisa configurations]
-
A.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
B.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset state.
-
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.
executionDevice
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
E.
launchDevice
Indicates initiating the operation or deployment of a device, typically starting its active functioning or sending it into its intended trajectory or mode of use.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3278bb8819098bbeac023410111 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.