Triple
T425297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Mini-B |
E8193
|
entity |
| Predicate | commonCableType |
P1373
|
FINISHED |
| Object | USB A to USB Mini-B cable |
—
|
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: USB A to USB Mini-B cable | Statement: [USB Mini-B, commonCableType, USB A to USB Mini-B cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCableType Context triple: [USB Mini-B, commonCableType, USB A to USB Mini-B cable]
-
A.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
E.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.