Triple
T12742597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slivovitz |
E304523
|
entity |
| Predicate | isRelatedToBeverage |
P70752
|
FINISHED |
| Object | rakija |
—
|
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: rakija | Statement: [Slivovitz, isRelatedToBeverage, rakija]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToBeverage Context triple: [Slivovitz, isRelatedToBeverage, rakija]
-
A.
hasBeverageReference
Indicates that one entity makes reference to, mentions, or is associated with a beverage in some way.
-
B.
hasBeverageCategory
chosen
Indicates that an entity is associated with or classified under a particular beverage category.
-
C.
isPackagedBeverage
Indicates that an item is a beverage that has been contained or sealed within some form of packaging for distribution or consumption.
-
D.
isNonHotBeverage
Indicates that a beverage is classified as not hot, typically being served at a cold or room temperature rather than heated.
-
E.
beverageSubcategory
Indicates a more specific classification within a broader beverage category, defining the subtype or subcategory of a 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.