Triple
T30015748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeagleBone Black |
E762589
|
entity |
| Predicate | bootSource |
P31985
|
FINISHED |
| Object | on-board eMMC |
—
|
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: on-board eMMC | Statement: [BeagleBone Black, bootSource, on-board eMMC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootSource Context triple: [BeagleBone Black, bootSource, on-board eMMC]
-
A.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
-
B.
bootIndicator
Indicates that a system, device, or component is in a state or condition related to its startup or boot process.
-
C.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
D.
bootCatalogLocation
Indicates the location or source from which a boot catalog (e.g., for system or media boot configuration) is stored or accessed.
-
E.
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).
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679844114819097242d623e723e4a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:45 p.m.