Triple
T30338920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POWER10 |
E771694
|
entity |
| Predicate | socketConfiguration |
P28422
|
FINISHED |
| Object | single-chip module |
—
|
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-chip module | Statement: [POWER10, socketConfiguration, single-chip module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socketConfiguration Context triple: [POWER10, socketConfiguration, single-chip module]
-
A.
socket
chosen
Indicates that one entity serves as a socket or receptacle into which another entity is designed to fit or connect.
-
B.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
C.
socketFamily
Indicates the type of communication protocol family (e.g., IPv4, IPv6, Unix domain) that a socket belongs to.
-
D.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
E.
connectionEstablishmentMethod
Indicates the method or mechanism by which a connection between entities is initiated or established.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681cf69588190b1a6373ddf29dd6a |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.