Triple
T7557489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revere Ware cookware |
E178704
|
entity |
| Predicate | heatSourceCompatibility |
P38384
|
FINISHED |
| Object | gas stoves |
—
|
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: gas stoves | Statement: [Revere Ware cookware, heatSourceCompatibility, gas stoves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatSourceCompatibility Context triple: [Revere Ware cookware, heatSourceCompatibility, gas stoves]
-
A.
heatSource
chosen
Indicates that one entity serves as a source of heat or heating for another entity.
-
B.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
-
C.
coolingRequirement
Indicates that an entity requires or is subject to a specific amount or type of cooling to operate within acceptable conditions.
-
D.
heatingMethod
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
-
E.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8db3d508190850ed41854d69838 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.