Triple
T27729458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juice Monster |
E697390
|
entity |
| Predicate | hasServingType |
P48322
|
FINISHED |
| Object | ready-to-drink can |
—
|
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: ready-to-drink can | Statement: [Juice Monster, hasServingType, ready-to-drink can]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServingType Context triple: [Juice Monster, hasServingType, ready-to-drink can]
-
A.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
hasServingCustom
Indicates that an entity follows or applies a particular custom, style, or convention in how something (such as food, drink, or service) is served.
-
C.
hasServingUse
Indicates that something is used or intended to be used for serving (e.g., food, drink, or portions).
-
D.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
E.
hasServingState
Indicates that an entity (such as a food or drink item) is associated with a particular state or condition in which it is served.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 3:10 p.m.