Triple
T28507656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unified Kernel Image specification |
E721400
|
entity |
| Predicate | bootEnvironment |
P37296
|
FINISHED |
| Object | UEFI |
—
|
NE NERFINISHED |
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: UEFI | Statement: [Unified Kernel Image specification, bootEnvironment, UEFI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootEnvironment Context triple: [Unified Kernel Image specification, bootEnvironment, UEFI]
-
A.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset state.
-
B.
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).
-
C.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
-
D.
launchEnvironment
chosen
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
bootMedium
Indicates that one entity serves as the medium or device from which another entity is booted or started.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f72cc848190bfb909c595cabefd |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:10 a.m.