Triple
T27885135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaby Lake Refresh |
E705203
|
entity |
| Predicate | TDPRange |
P76360
|
FINISHED |
| Object | 15 W nominal TDP |
—
|
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: 15 W nominal TDP | Statement: [Kaby Lake Refresh, TDPRange, 15 W nominal TDP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TDPRange Context triple: [Kaby Lake Refresh, TDPRange, 15 W nominal TDP]
-
A.
targetTDPRange
chosen
Indicates the specified thermal design power (TDP) range that a component or system is intended or required to operate within.
-
B.
configurableTDPDown
Indicates that the entity supports reducing its thermal design power (TDP) to a configurable lower limit for power or thermal management.
-
C.
tdp
Indicates a temporal dependency or precedence relation where one event or process must occur before or in coordination with another.
-
D.
configurableTDPUp
Indicates that the thermal design power (TDP) of a component can be increased above its default level through configuration or settings.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639b09d208190a78de29906514a12 |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:32 p.m.