Triple
T31474120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ampere Altra |
E802943
|
entity |
| Predicate | socketType |
P1374
|
FINISHED |
| Object | single-socket |
—
|
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: single-socket | Statement: [Ampere Altra, socketType, single-socket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socketType Context triple: [Ampere Altra, socketType, single-socket]
-
A.
socket
Indicates that one entity serves as a socket or receptacle into which another entity is designed to fit or connect.
-
B.
socketFamily
Indicates the type of communication protocol family (e.g., IPv4, IPv6, Unix domain) that a socket belongs to.
-
C.
packetType
Indicates the specific category or kind of data packet involved in a communication or transmission.
-
D.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
E.
portTypes
Indicates that two entities are associated through specific types of ports or interfaces used for connection or communication.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:28 p.m.