Triple
T19418145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornish clotted cream |
E485773
|
entity |
| Predicate | PDOMilkRequirement |
P135799
|
FINISHED |
| Object | must be made from milk produced in Cornwall |
—
|
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: must be made from milk produced in Cornwall | Statement: [Cornish clotted cream, PDOMilkRequirement, must be made from milk produced in Cornwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PDOMilkRequirement Context triple: [Cornish clotted cream, PDOMilkRequirement, must be made from milk produced in Cornwall]
-
A.
milkType
Indicates the specific kind or category of milk associated with an entity (e.g., whole, skim, plant-based).
-
B.
milkComposition
Indicates the specific nutrients and components that make up a given sample of milk.
-
C.
typicalMilkSource
Indicates that one entity is the usual or primary source from which the other entity obtains milk.
-
D.
milkTreatment
Indicates that an entity is subjected to a process or method of treating or processing milk.
-
E.
primaryDairyBase
Indicates that one entity serves as the main dairy ingredient or foundational dairy component used in or associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62afad8d881908f1de6324e55d2f6 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.