Triple
T29390458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD Express |
E745356
|
entity |
| Predicate | supportsBusMode |
P99857
|
FINISHED |
| Object | PCIe/NVMe mode |
—
|
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: PCIe/NVMe mode | Statement: [SD Express, supportsBusMode, PCIe/NVMe mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusMode Context triple: [SD Express, supportsBusMode, PCIe/NVMe mode]
-
A.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
B.
supportedBusInterface
Indicates that one entity provides or is compatible with a particular bus interface used for communication or connection with other components.
-
C.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
D.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
E.
hasBusType
Indicates that one entity (typically a bus or bus service) is associated with or classified by a specific type or category of bus.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
Created at: April 28, 2026, 2:42 p.m.