Triple
T32870498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | feijoada |
E840775
|
entity |
| Predicate | typicalDrinkPairing |
P200236
|
FINISHED |
| Object | caipirinha |
E292792
|
NE 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: caipirinha | Statement: [feijoada, typicalDrinkPairing, caipirinha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDrinkPairing Context triple: [feijoada, typicalDrinkPairing, caipirinha]
-
A.
typicalFoodPairing
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
B.
drinksWith
Indicates that two entities consume beverages together, typically at the same time and place in a social context.
-
C.
winePairing
Indicates a relationship where a particular wine is recommended as a suitable accompaniment for a given food or dish.
-
D.
typicalDrinkOption
chosen
Indicates that something is a common or standard choice among available drink options.
-
E.
commonCocktail
Indicates that the related entities are ingredients or components that commonly appear together in the same cocktail.
- F. None of above.
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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34bd1559b08190895827863a22d421 |
completed | June 19, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:17 a.m.