Triple
T2106844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora CoreOS |
E42412
|
entity |
| Predicate | bootProcess |
P35870
|
FINISHED |
| Object | Ignition runs on first boot |
—
|
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: Ignition runs on first boot | Statement: [Fedora CoreOS, bootProcess, Ignition runs on first boot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootProcess Context triple: [Fedora CoreOS, bootProcess, Ignition runs on first boot]
-
A.
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).
-
B.
bootTimeCharacteristic
Indicates the duration or properties of the time it takes a system or device to start up from an inactive state.
-
C.
bootMedium
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
D.
primaryProcess
Indicates that one process is the main or most fundamental process in relation to another process or within a given system or context.
-
E.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
- F. None of above. chosen
Provenance (4 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbadf12b88190acc513d8512777b2 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb9ce3ff08190a9501f8bb821c01c |
completed | March 7, 2026, 5:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.