Triple
T8611465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD Association |
E203922
|
entity |
| Predicate | standardizes |
P1371
|
FINISHED |
| Object |
UHS-I
UHS-I is a high-speed bus interface standard for SD memory cards that significantly increases data transfer rates compared to earlier SD specifications.
|
E745355
|
NE FINISHED |
How this triple was built (4 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 | Statement: [SD Association, standardizes, UHS-I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UHS-I Context triple: [SD Association, standardizes, UHS-I]
-
A.
UHS
UHS is the stock ticker symbol for Universal Health Services, a major U.S.-based hospital and healthcare services company.
-
B.
U.2
U.2 is a computer storage interface standard used primarily to connect high-performance NVMe solid-state drives to enterprise servers via a 2.5-inch form factor.
-
C.
UFS
UFS (Unix File System) is a long-standing, robust file system widely used in Unix-like operating systems, particularly BSD variants, for organizing and managing data on disk.
-
D.
USB 3.1
USB 3.1 is a high-speed Universal Serial Bus standard that introduced up to 10 Gbit/s data transfer rates and improved power delivery over its predecessors.
-
E.
U3
U3 is one of the main lines of the Nuremberg U-Bahn rapid transit system in Nuremberg, Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: UHS-I Triple: [SD Association, standardizes, UHS-I]
Generated description
UHS-I is a high-speed bus interface standard for SD memory cards that significantly increases data transfer rates compared to earlier SD specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: UHS-I Target entity description: UHS-I is a high-speed bus interface standard for SD memory cards that significantly increases data transfer rates compared to earlier SD specifications.
-
A.
UHS
UHS is the stock ticker symbol for Universal Health Services, a major U.S.-based hospital and healthcare services company.
-
B.
U.2
U.2 is a computer storage interface standard used primarily to connect high-performance NVMe solid-state drives to enterprise servers via a 2.5-inch form factor.
-
C.
UFS
UFS (Unix File System) is a long-standing, robust file system widely used in Unix-like operating systems, particularly BSD variants, for organizing and managing data on disk.
-
D.
USB 3.1
USB 3.1 is a high-speed Universal Serial Bus standard that introduced up to 10 Gbit/s data transfer rates and improved power delivery over its predecessors.
-
E.
U3
U3 is one of the main lines of the Nuremberg U-Bahn rapid transit system in Nuremberg, Germany.
- F. None of above. chosen
Provenance (5 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea91456a88190a7416b0f1a0327d6 |
completed | April 2, 2026, 5:36 p.m. |
| NEDg | Description generation | batch_69cea9e685388190a4be9d2135dc02d0 |
completed | April 2, 2026, 5:39 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ceaababe2c8190bc47430d33bfdbaa |
completed | April 2, 2026, 5:43 p.m. |
Created at: March 30, 2026, 6:25 p.m.