Triple
T29956535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volí Vodka |
E760915
|
entity |
| Predicate | hasIngredientBase |
P12771
|
FINISHED |
| Object | grain alcohol |
—
|
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: grain alcohol | Statement: [Volí Vodka, hasIngredientBase, grain alcohol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIngredientBase Context triple: [Volí Vodka, hasIngredientBase, grain alcohol]
-
A.
hasMainIngredient
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
hasKeyIngredientAttribute
Indicates that an entity possesses a specific key ingredient as a defining attribute or component.
-
C.
hasVariantIngredient
Indicates that one ingredient is an alternative or substitute form of another ingredient used in a product or formulation.
-
D.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
E.
usesIngredientInfluenceFrom
Indicates that one entity incorporates or applies the influence, properties, or effects derived from a particular ingredient in its action or outcome.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: April 29, 2026, 6:27 p.m.