Triple
T19056048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Roses Distillery |
E466397
|
entity |
| Predicate | usesRecipeCount |
P88940
|
FINISHED |
| Object | 10 distinct bourbon recipes |
—
|
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: 10 distinct bourbon recipes | Statement: [Four Roses Distillery, usesRecipeCount, 10 distinct bourbon recipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRecipeCount Context triple: [Four Roses Distillery, usesRecipeCount, 10 distinct bourbon recipes]
-
A.
numberOfRecipes
chosen
Indicates the quantity of recipes associated with a given entity.
-
B.
usesRecipeOf
Indicates that one entity prepares or creates something by following the recipe or formula originally defined or used by another entity.
-
C.
usesIngredientInfluenceFrom
Indicates that one entity incorporates or applies the influence, properties, or effects derived from a particular ingredient in its action or outcome.
-
D.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
E.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc056b708190a2b84cbddf0fc2d9 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.