Triple
T29390398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHS-I |
E745355
|
entity |
| Predicate | supportsBusSpeedMode |
P31519
|
FINISHED |
| Object | SDR12 |
—
|
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: SDR12 | Statement: [UHS-I, supportsBusSpeedMode, SDR12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusSpeedMode Context triple: [UHS-I, supportsBusSpeedMode, SDR12]
-
A.
supportsBusSpeed
chosen
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
B.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
C.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
D.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
E.
supportsMultipleBusMasters
Indicates that the system or component allows more than one bus master to control or access the bus concurrently or in turn.
- 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_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
Created at: April 28, 2026, 2:41 p.m.