Triple
T14576909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan (cocktail) |
E342075
|
entity |
| Predicate | usesVermouthType |
P114926
|
FINISHED |
| Object | Italian sweet vermouth |
—
|
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: Italian sweet vermouth | Statement: [Manhattan (cocktail), usesVermouthType, Italian sweet vermouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVermouthType Context triple: [Manhattan (cocktail), usesVermouthType, Italian sweet vermouth]
-
A.
usesWineType
Indicates that one entity makes use of, incorporates, or is associated with a particular type or category of wine.
-
B.
wineTypeAllowed
Indicates that a particular type of wine is permitted or acceptable in a given context or for a given purpose.
-
C.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
D.
sparklingWineAllowed
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
-
E.
hasSparklingWine
Indicates that an entity possesses, includes, or is associated with sparkling wine.
- F. None of above. chosen
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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f5ec448190b2ef887fdf7b633e |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.