Triple
T30364022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POWER8 |
E772365
|
entity |
| Predicate | hasMaxCoresPerChip |
P159947
|
FINISHED |
| Object | up to 12 cores |
—
|
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: up to 12 cores | Statement: [POWER8, hasMaxCoresPerChip, up to 12 cores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxCoresPerChip Context triple: [POWER8, hasMaxCoresPerChip, up to 12 cores]
-
A.
maxCoresPerChiplet
Indicates the maximum number of processing cores that are allowed or supported on a single chiplet.
-
B.
maxCoreCountPerCPU
chosen
Indicates the maximum number of processing cores that a single CPU is allowed or configured to have.
-
C.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
D.
isMultiCore
Indicates that the entity (such as a processor or system) consists of or utilizes multiple processing cores operating together.
-
E.
supportsCoreCountUpTo
Indicates that an entity is capable of functioning correctly with, or providing compatibility for, processor configurations up to a specified maximum number of cores.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: April 29, 2026, 7:58 p.m.