Triple
T25425159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denverton platform |
E637098
|
entity |
| Predicate | processorCoreType |
P11226
|
FINISHED |
| Object | Goldmont 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: Goldmont core | Statement: [Denverton platform, processorCoreType, Goldmont core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processorCoreType Context triple: [Denverton platform, processorCoreType, Goldmont core]
-
A.
CPUType
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
B.
CPUCoreConfiguration
Indicates the specific arrangement and characteristics of processor cores allocated or defined within a computing system.
-
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.
cpuImplementation
Indicates that one entity serves as the hardware or architectural realization (implementation) of a specified CPU design or model.
-
E.
cpuCoreMicroarchitecture
chosen
Indicates the specific microarchitecture design implemented in a given CPU core.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:57 p.m.