Triple
T30364023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POWER8 |
E772365
|
entity |
| Predicate | hasThreadsPerCore |
P113025
|
FINISHED |
| Object | up to 8 threads per core |
—
|
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 8 threads per core | Statement: [POWER8, hasThreadsPerCore, up to 8 threads per core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreadsPerCore Context triple: [POWER8, hasThreadsPerCore, up to 8 threads per core]
-
A.
threadsPerCore
chosen
Indicates the number of hardware or logical execution threads that are assigned to run on each individual processor core.
-
B.
totalHardwareThreads
Indicates the total number of hardware execution threads (e.g., logical CPU cores) available on a processing unit or system.
-
C.
isMultiCore
Indicates that the entity (such as a processor or system) consists of or utilizes multiple processing cores operating together.
-
D.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
E.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 7:58 p.m.