Triple
T32147324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crème brûlée |
E821054
|
entity |
| Predicate | commonFlavorVariant |
P154687
|
FINISHED |
| Object | coffee crème brûlée |
—
|
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: coffee crème brûlée | Statement: [crème brûlée, commonFlavorVariant, coffee crème brûlée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFlavorVariant Context triple: [crème brûlée, commonFlavorVariant, coffee crème brûlée]
-
A.
isFlavouredVariantOf
chosen
Indicates that one item is a version of another that has been modified or distinguished specifically by added or altered flavor characteristics.
-
B.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
C.
isOfficialFlavorOf
Indicates that one item is formally recognized or designated as an official flavor associated with another entity (such as a brand, product line, or event).
-
D.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
-
E.
intendedFlavorProfile
Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 1, 2026, 12:31 a.m.