Triple
T29390408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHS-I |
E745355
|
entity |
| Predicate | requiresHostSupport |
P11374
|
FINISHED |
| Object | UHS-I capable SD host controller |
—
|
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: UHS-I capable SD host controller | Statement: [UHS-I, requiresHostSupport, UHS-I capable SD host controller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresHostSupport Context triple: [UHS-I, requiresHostSupport, UHS-I capable SD host controller]
-
A.
supportsHostType
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified host type.
-
B.
hostRequirement
chosen
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
-
C.
supportsConfigurationFromHost
Indicates that an entity can accept and operate using configuration settings provided by a host system.
-
D.
supportsHostManagement
Indicates that an entity provides functionality to manage, configure, or control a host system or environment.
-
E.
qualifiedAsHost
Indicates that an entity has met the necessary criteria or standards to serve in the role of a host.
- 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_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 2:41 p.m.