Triple
T2105917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC AT |
E37193
|
entity |
| Predicate | keyboardConnector |
P1374
|
FINISHED |
| Object | 5-pin 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: 5-pin DIN keyboard connector | Statement: [IBM PC AT, keyboardConnector, 5-pin DIN keyboard connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyboardConnector Context triple: [IBM PC AT, keyboardConnector, 5-pin DIN keyboard connector]
-
A.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
B.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
C.
hostSideConnector
Indicates a connector that is located on or associated with the host side of a connection or interface.
-
D.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbaddeb148190b728bce7a7b041fb |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.