Triple
T25931380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HT Technology |
E653445
|
entity |
| Predicate | logicalProcessorRatio |
P159574
|
FINISHED |
| Object | typically two logical processors per physical 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: typically two logical processors per physical core | Statement: [HT Technology, logicalProcessorRatio, typically two logical processors per physical core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalProcessorRatio Context triple: [HT Technology, logicalProcessorRatio, typically two logical processors per physical core]
-
A.
coreCountCPU
Indicates the number of processing cores that a CPU has.
-
B.
gpuCoreCount
Indicates the number of processing cores present in a GPU.
-
C.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
D.
efficiencyCores
Indicates that the related cores are optimized for energy-efficient, low-power processing rather than maximum performance.
-
E.
supportsIntelHyperThreading
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
- 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_69f604192b6c8190b86e151a628eafd8 |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:37 a.m.