Triple
T29390031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Digital |
E745348
|
entity |
| Predicate | supportsBusInterface |
P193521
|
FINISHED |
| Object | Default Speed |
—
|
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: Default Speed | Statement: [Secure Digital, supportsBusInterface, Default Speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusInterface Context triple: [Secure Digital, supportsBusInterface, Default Speed]
-
A.
supportedBusInterface
chosen
Indicates that one entity provides or is compatible with a particular bus interface used for communication or connection with other components.
-
B.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
C.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
D.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
E.
hasBusArchitecture
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
- 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_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: April 28, 2026, 2:41 p.m.