Triple
T25876378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modica chocolate |
E651912
|
entity |
| Predicate | tempering |
P153354
|
FINISHED |
| Object | not traditionally tempered |
—
|
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: not traditionally tempered | Statement: [Modica chocolate, tempering, not traditionally tempered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempering Context triple: [Modica chocolate, tempering, not traditionally tempered]
-
A.
temperingPurpose
Indicates that one entity undergoes a tempering process specifically for the purpose or intended function defined by another entity or condition.
-
B.
temper
Indicates moderating, softening, or counterbalancing the intensity, effect, or quality of something through the influence of something else.
-
C.
firingTemperature
Indicates the temperature at which a material or object is heated during a firing process (such as in a kiln or furnace).
-
D.
temperatureDependent
Indicates that the existence, intensity, or outcome of a relationship or process varies as a function of temperature.
-
E.
isHeatTreated
chosen
Indicates that an entity has undergone a heat treatment process to alter its physical or mechanical properties.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602e04d3481909c7de02ca6b680c7 |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:12 a.m.