Triple
T5589788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldspot refrigerator for Sears |
E146845
|
entity |
| Predicate | refrigerationType |
P11564
|
FINISHED |
| Object | vapor-compression refrigeration |
—
|
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: vapor-compression refrigeration | Statement: [Coldspot refrigerator for Sears, refrigerationType, vapor-compression refrigeration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refrigerationType Context triple: [Coldspot refrigerator for Sears, refrigerationType, vapor-compression refrigeration]
-
A.
furnaceType
Indicates the specific kind or category of furnace associated with an entity.
-
B.
coolingMethod
chosen
Indicates the technique or process used to remove heat from something or keep it at a lower temperature.
-
C.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
D.
hasIceShelf
Indicates that a glacier, ice sheet, or coastline possesses an attached floating extension of ice known as an ice shelf.
-
E.
heatingMethod
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0209ff5d88190843b6d134390ab71 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.