Triple
T8247942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | systemd-boot |
E192892
|
entity |
| Predicate | canBeInstalledTo |
P31902
|
FINISHED |
| Object | EFI System Partition |
—
|
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: EFI System Partition | Statement: [systemd-boot, canBeInstalledTo, EFI System Partition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeInstalledTo Context triple: [systemd-boot, canBeInstalledTo, EFI System Partition]
-
A.
supportsInstallation
chosen
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
-
B.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
C.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
D.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
E.
installationSpace
Indicates the physical or virtual area required or designated for installing an object, system, or component.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.