Triple
T321553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-B |
E6424
|
entity |
| Predicate | hostSideConnector |
P11995
|
FINISHED |
| Object | usually USB Type-A |
—
|
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: usually USB Type-A | Statement: [USB Type-B, hostSideConnector, usually USB Type-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSideConnector Context triple: [USB Type-B, hostSideConnector, usually USB Type-A]
-
A.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
B.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
hostState
Indicates a relationship where one entity serves as the host or governing state for another entity, within whose jurisdiction, territory, or authority that other entity operates or resides.
-
D.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
E.
hostsUnit
Indicates that one entity serves as the location or container in which another unit is situated, operates, or is organized.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.