Triple
T8210255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROM BIOS |
E191794
|
entity |
| Predicate | userConfigurableVia |
P33710
|
FINISHED |
| Object | BIOS setup program |
—
|
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: BIOS setup program | Statement: [ROM BIOS, userConfigurableVia, BIOS setup program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userConfigurableVia Context triple: [ROM BIOS, userConfigurableVia, BIOS setup program]
-
A.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
B.
customizableBy
chosen
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
C.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
D.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
E.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.