Triple
T1789412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serial ATA |
E39460
|
entity |
| Predicate | physicalConnector |
P1374
|
FINISHED |
| Object | 7-pin data 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: 7-pin data connector | Statement: [Serial ATA, physicalConnector, 7-pin data connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalConnector Context triple: [Serial ATA, physicalConnector, 7-pin data connector]
-
A.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
B.
hasPhysicalFootprint
Indicates that one entity occupies or affects a specific physical area or space in the real world.
-
C.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
D.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
E.
physicalLayer
Indicates a relationship where one entity functions as or pertains to the lowest (physical) layer in a layered system or communication stack, handling the actual transmission of signals or raw data.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.