Triple
T8472649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centronics parallel port |
E200314
|
entity |
| Predicate | hostSideConnectorType |
P11995
|
FINISHED |
| Object | DB-25 female 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: DB-25 female connector | Statement: [Centronics parallel port, hostSideConnectorType, DB-25 female connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSideConnectorType Context triple: [Centronics parallel port, hostSideConnectorType, DB-25 female connector]
-
A.
hostSideConnector
chosen
Indicates a connector that is located on or associated with the host side of a connection or interface.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
D.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.