Triple
T32988236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS/2 |
E844005
|
entity |
| Predicate | introducedConnectorType |
P45161
|
FINISHED |
| Object | 6-pin mini-DIN keyboard connector |
—
|
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: 6-pin mini-DIN keyboard connector | Statement: [PS/2, introducedConnectorType, 6-pin mini-DIN keyboard connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedConnectorType Context triple: [PS/2, introducedConnectorType, 6-pin mini-DIN keyboard connector]
-
A.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
B.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
C.
connectorTypeDesignation
chosen
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
D.
introducedAsType
Indicates that one entity is presented or identified to others as having a particular role, category, or type.
-
E.
isMajorConnectorFor
Indicates that one entity serves as a primary or critical linkage or pathway connecting other entities within a system or network.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.