Triple
T28610955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qemu-nbd |
E724165
|
entity |
| Predicate | optionExample |
P83556
|
FINISHED |
| Object | --connect to attach an image to an /dev/nbdX device |
—
|
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: --connect to attach an image to an /dev/nbdX device | Statement: [qemu-nbd, optionExample, --connect to attach an image to an /dev/nbdX device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionExample Context triple: [qemu-nbd, optionExample, --connect to attach an image to an /dev/nbdX device]
-
A.
modeExamples
Indicates that specific example instances are provided to illustrate or clarify a particular mode or manner in which something operates or occurs.
-
B.
optionedBy
Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
-
C.
optionType
Indicates the specific category or kind an option belongs to within a set of possible choices.
-
D.
valueExample
chosen
Indicates that something is provided as an illustrative or sample instance of a particular value.
-
E.
typicalOption
Indicates that one option is considered standard, common, or most representative among a set of possible options.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:30 a.m.