Triple
T30422199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam440ep motherboard |
E773928
|
entity |
| Predicate | bootFirmware |
P65185
|
FINISHED |
| Object | U-Boot |
—
|
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: U-Boot | Statement: [Sam440ep motherboard, bootFirmware, U-Boot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootFirmware Context triple: [Sam440ep motherboard, bootFirmware, U-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.
bootProcess
Indicates the sequence of actions required to start up and initialize a system from a powered-off or reset state.
-
C.
firmware
chosen
Indicates that one entity serves as the firmware (embedded low-level control software) for another entity.
-
D.
bootFirmwarePolicy
Indicates the policy or rules governing how firmware is loaded and executed during the system boot process.
-
E.
bootFeature
Indicates that an entity provides or is associated with a specific feature or capability available at system boot time.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68663d49c81908c44b8cb0f31d014 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:06 p.m.