Triple
T25932395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen |
E653467
|
entity |
| Predicate | supportsCoreCountUpTo |
P192271
|
FINISHED |
| Object | 32 cores in EPYC 7001 series |
—
|
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: 32 cores in EPYC 7001 series | Statement: [Zen, supportsCoreCountUpTo, 32 cores in EPYC 7001 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCoreCountUpTo Context triple: [Zen, supportsCoreCountUpTo, 32 cores in EPYC 7001 series]
-
A.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
B.
bigCoreCount
Indicates that an entity (such as a processor or system) has a relatively large number of cores compared to a typical or baseline configuration.
-
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.
smallCoreCount
Indicates that an entity has a relatively low number of processing cores compared to typical or expected configurations.
-
E.
isMultiCore
Indicates that the entity (such as a processor or system) consists of or utilizes multiple processing cores operating together.
- F. None of above. chosen
Provenance (4 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 22, 2026, 8:37 a.m.