Triple
T27811186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milk Stand |
E702521
|
entity |
| Predicate | basedOnFictionalBeverageFrom |
P182222
|
FINISHED |
| Object | Star Wars film series |
—
|
NE NERFINISHED |
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: Star Wars film series | Statement: [Milk Stand, basedOnFictionalBeverageFrom, Star Wars film series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnFictionalBeverageFrom Context triple: [Milk Stand, basedOnFictionalBeverageFrom, Star Wars film series]
-
A.
hasDrinkNamedAfter
Indicates that one entity has a beverage that is named after another entity.
-
B.
isSoftDrinkVariantOf
Indicates that one soft drink is a specific version, flavor, or formulation derived from or based on another soft drink.
-
C.
beverageBase
Indicates that one entity serves as the primary liquid or foundational ingredient used to make a beverage involving the other entity.
-
D.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
E.
hasBeverageReference
Indicates that one entity makes reference to, mentions, or is associated with a beverage in some way.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 27, 2026, 5:42 p.m.