Triple
T26508189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Orange Edition |
E669607
|
entity |
| Predicate | typicalServingContainer |
P34427
|
FINISHED |
| Object | slim 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: slim can | Statement: [Red Bull Orange Edition, typicalServingContainer, slim can]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServingContainer Context triple: [Red Bull Orange Edition, typicalServingContainer, slim can]
-
A.
servingVessel
Indicates that one entity functions as the container or vessel used to serve another entity (such as food or drink).
-
B.
marketedAsServing
Indicates that something is promoted or advertised as providing service to a particular audience, purpose, or function.
-
C.
typicalPortionPerBowl
Indicates the usual or standard quantity served in a single bowl for a given item or context.
-
D.
servingStyle
Indicates how something (typically food or drink) is presented or offered for consumption or use.
-
E.
containerType
chosen
Indicates the specific kind or category of container associated with or used to hold an 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: April 27, 2026, 1:18 a.m.