Triple
T321563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-B |
E6424
|
entity |
| Predicate | electricalInterface |
P1374
|
FINISHED |
| Object | USB serial bus |
—
|
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 serial bus | Statement: [USB Type-B, electricalInterface, USB serial bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricalInterface Context triple: [USB Type-B, electricalInterface, USB serial bus]
-
A.
electrificationSystem
Indicates the type of electrical power system used to supply energy (typically to infrastructure or vehicles) for operation.
-
B.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
C.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
E.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.