Triple
T13320061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threadripper |
E317290
|
entity |
| Predicate | typicalCoreCountRange |
P100845
|
FINISHED |
| Object | high core count |
—
|
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: high core count | Statement: [Threadripper, typicalCoreCountRange, high core count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCoreCountRange Context triple: [Threadripper, typicalCoreCountRange, high core count]
-
A.
bigCoreCount
chosen
Indicates that an entity (such as a processor or system) has a relatively large number of cores compared to a typical or baseline configuration.
-
B.
gpuCoreCount
Indicates the number of processing cores present in a GPU.
-
C.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
D.
coreCountCPU
Indicates the number of processing cores that a CPU has.
-
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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.