Triple
T25425135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Lake |
E637097
|
entity |
| Predicate | thermalDesignPowerRange |
P76360
|
FINISHED |
| Object | 4 W to 10 W |
—
|
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: 4 W to 10 W | Statement: [Apollo Lake, thermalDesignPowerRange, 4 W to 10 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalDesignPowerRange Context triple: [Apollo Lake, thermalDesignPowerRange, 4 W to 10 W]
-
A.
targetTDPRange
chosen
Indicates the specified thermal design power (TDP) range that a component or system is intended or required to operate within.
-
B.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
C.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
D.
heatOutputRange
Indicates the range of heat energy or thermal power that an entity can produce or emit under specified conditions.
-
E.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:57 p.m.