Triple
T28246330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i7-8500Y |
E712177
|
entity |
| Predicate | supportsIntelHyper-ThreadingTechnology |
P80134
|
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 i7-8500Y, supportsIntelHyper-ThreadingTechnology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntelHyper-ThreadingTechnology Context triple: [Intel Core i7-8500Y, supportsIntelHyper-ThreadingTechnology, true]
-
A.
supportsIntelHyperThreading
chosen
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
-
B.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
C.
supportsIntelTurboBoost
Indicates that one entity provides compatibility with or functional support for Intel Turbo Boost technology in relation to another entity.
-
D.
supportsIntelTurboBoostTechnology2.0
Indicates that one entity provides compatibility with or enables the use of Intel Turbo Boost Technology 2.0 for another entity.
-
E.
supportsIntelTSX-NI
Indicates that one entity provides or is compatible with Intel TSX-NI (Transactional Synchronization Extensions New Instructions) functionality for another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: April 27, 2026, 11:01 p.m.