Triple
T37625325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rittenhouse Rye |
E936190
|
entity |
| Predicate | notableCocktail |
P148290
|
FINISHED |
| Object | Manhattan |
E342075
|
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: Manhattan | Statement: [Rittenhouse Rye, notableCocktail, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCocktail Context triple: [Rittenhouse Rye, notableCocktail, Manhattan]
-
A.
commonCocktail
Indicates that the related entities are ingredients or components that commonly appear together in the same cocktail.
-
B.
IBAOfficialCocktail
Indicates that a cocktail is officially recognized and listed by the International Bartenders Association (IBA) as part of its standard repertoire.
-
C.
notableCocktailUse
chosen
Indicates that something is significantly or famously used as an ingredient or component in a particular cocktail.
-
D.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
E.
cocktailStyle
Indicates that one entity is characterized by, prepared in, or associated with the cocktail style of another entity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba37063881908f43a523cdf1740c |
completed | June 28, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.