Triple
T31847925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Configuration |
E812988
|
entity |
| Predicate | BootTabFeature |
P169148
|
FINISHED |
| Object | Safe boot options |
—
|
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: Safe boot options | Statement: [System Configuration, BootTabFeature, Safe boot options]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BootTabFeature Context triple: [System Configuration, BootTabFeature, Safe boot options]
-
A.
bossFeature
Indicates that one entity serves as a primary or dominant feature, element, or component in relation to another.
-
B.
bootFeature
chosen
Indicates that an entity provides or is associated with a specific feature or capability available at system boot time.
-
C.
shellFeature
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
-
D.
launcherFeature
Indicates that one entity functions as a feature, capability, or component provided by a launcher or launching system for another entity.
-
E.
documentedFeature
Indicates that a feature has been formally recorded or described in documentation.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b037fb0c81909f65de547ea3a5d8 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:50 p.m.