Triple
T18756324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bean Eater |
E458657
|
entity |
| Predicate | drinkDepicted |
P14783
|
FINISHED |
| Object | wine or water in jug |
—
|
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: wine or water in jug | Statement: [The Bean Eater, drinkDepicted, wine or water in jug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drinkDepicted Context triple: [The Bean Eater, drinkDepicted, wine or water in jug]
-
A.
drinkFamily
Indicates a familial or close relational connection between two entities centered around drinking-related activities or contexts.
-
B.
alcoholType
chosen
Indicates the specific kind or category of alcohol associated with an entity (e.g., beer, wine, spirits).
-
C.
madeWithAlcohol
Indicates that something is created, prepared, or produced using alcohol as an ingredient or component.
-
D.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
E.
isAlcoholicBeverage
Indicates that a beverage contains alcohol and is classified as an alcoholic drink.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f20b808190833e29830bfed937 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.