Triple
T11427799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee's Best |
E270797
|
entity |
| Predicate | intendedServingGlass |
P72115
|
FINISHED |
| Object | pint 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: pint glass | Statement: [Milwaukee's Best, intendedServingGlass, pint glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedServingGlass Context triple: [Milwaukee's Best, intendedServingGlass, pint glass]
-
A.
servingVessel
chosen
Indicates that one entity functions as the container or vessel used to serve another entity (such as food or drink).
-
B.
pouredOutBy
Indicates that a substance or liquid was released or emptied from a container or source by a particular agent or entity.
-
C.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
D.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
E.
servesWith
Indicates that one entity is customarily presented, used, or consumed together with another as a complementary accompaniment.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c000b88190bfaa646b2dc424b7 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.