Triple
T16246085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinsault |
E394373
|
entity |
| Predicate | hasTypicalServingTemperature |
P66977
|
FINISHED |
| Object | slightly chilled for light reds |
—
|
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: slightly chilled for light reds | Statement: [Cinsault, hasTypicalServingTemperature, slightly chilled for light reds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalServingTemperature Context triple: [Cinsault, hasTypicalServingTemperature, slightly chilled for light reds]
-
A.
recommendedServingTemperature
chosen
Indicates the temperature at which something (typically food or drink) is advised to be served for optimal use or enjoyment.
-
B.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
-
C.
servedHot
Indicates that something is provided or presented in a heated or warm state, suitable for immediate consumption.
-
D.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
E.
servingStyle
Indicates how something (typically food or drink) is presented or offered for consumption or use.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24561d250819096f709ea8751fcb9 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.