Triple
T25932448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen 2 |
E653468
|
entity |
| Predicate | maxThreadsPerCore |
P113025
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Zen 2, maxThreadsPerCore, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxThreadsPerCore Context triple: [Zen 2, maxThreadsPerCore, 2]
-
A.
threadsPerCore
chosen
Indicates the number of hardware or logical execution threads that are assigned to run on each individual processor core.
-
B.
maxCoresPerCluster
Indicates the maximum number of processing cores that are allowed or allocated within a single cluster.
-
C.
maxNumberOfProcessors
Indicates the maximum number of processors that are allowed or supported in a given context or configuration.
-
D.
totalHardwareThreads
Indicates the total number of hardware execution threads (e.g., logical CPU cores) available on a processing unit or system.
-
E.
threadCount
Indicates the number of concurrent threads associated with an entity, such as a process, task, or execution context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60419ef7881909fe061a3d1aa1ddf |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:37 a.m.