Triple
T33751073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginjinha |
E864842
|
entity |
| Predicate | servingOption |
P14779
|
FINISHED |
| Object | with cherry in the glass |
—
|
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: with cherry in the glass | Statement: [Ginjinha, servingOption, with cherry in the glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingOption Context triple: [Ginjinha, servingOption, with cherry in the glass]
-
A.
servingStyle
chosen
Indicates how something (typically food or drink) is presented or offered for consumption or use.
-
B.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
C.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
D.
servesProduct
Indicates that one entity provides or offers a particular product to others, typically in a commercial or service context.
-
E.
servesSide
Indicates that one entity is provided or presented as an accompanying side item to another primary entity.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:45 a.m.