Triple
T26212593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen 3 |
E655526
|
entity |
| Predicate | socketSupport |
P97615
|
FINISHED |
| Object |
SP3
SP3 is AMD’s high-pin-count server CPU socket used primarily for EPYC processors in data center and enterprise platforms.
|
E1714641
|
NE FINISHED |
How this triple was built (3 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: SP3 | Statement: [Zen 3, socketSupport, SP3]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SP3 Triple: [Zen 3, socketSupport, SP3]
Generated description
SP3 is AMD’s high-pin-count server CPU socket used primarily for EPYC processors in data center and enterprise platforms.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socketSupport Context triple: [Zen 3, socketSupport, SP3]
-
A.
socket
Indicates that one entity serves as a socket or receptacle into which another entity is designed to fit or connect.
-
B.
supportsPort
chosen
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
C.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
-
E.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
- F. None of above.
Provenance (6 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11858b71f48190bd979be75d984930 |
completed | May 23, 2026, 10:46 a.m. |
| NEDg | Description generation | batch_6a11865aaac881909aa388f473a6e5a3 |
completed | May 23, 2026, 10:50 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a11873fe9708190a0ad2b27028b120a |
completed | May 23, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:53 p.m.