Triple
T26123391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denomination of Origin Tequila |
E659036
|
entity |
| Predicate | mainIngredientRequired |
P5291
|
FINISHED |
| Object | blue agave |
—
|
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: blue agave | Statement: [Denomination of Origin Tequila, mainIngredientRequired, blue agave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainIngredientRequired Context triple: [Denomination of Origin Tequila, mainIngredientRequired, blue agave]
-
A.
hasMainIngredient
chosen
Indicates that one entity is the primary or most significant ingredient used to make another entity.
-
B.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
C.
preparationRequirement
Indicates that one entity must be prepared, configured, or made ready as a necessary condition before another entity, action, or process can occur or be valid.
-
D.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
E.
bloodMealRequirement
Indicates that an organism requires a blood meal, typically for development, reproduction, or survival.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:10 p.m.