Triple
T32235850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i5-1235U |
E823463
|
entity |
| Predicate | supportsHyperThreadingOnPCores |
P80122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Intel Core i5-1235U, supportsHyperThreadingOnPCores, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHyperThreadingOnPCores Context triple: [Intel Core i5-1235U, supportsHyperThreadingOnPCores, true]
-
A.
supportsHyperThreading
chosen
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
B.
supportsIntelHyperThreading
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
-
C.
supportsProcessorCoreCount
Indicates that one entity is compatible with or able to operate using a specified number of processor cores in another entity.
-
D.
totalHardwareThreads
Indicates the total number of hardware execution threads (e.g., logical CPU cores) available on a processing unit or system.
-
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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:39 a.m.