Triple
T27729821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipeline Punch |
E697399
|
entity |
| Predicate | containsArtificialSweeteners |
P193407
|
FINISHED |
| Object | may vary by market |
—
|
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: may vary by market | Statement: [Pipeline Punch, containsArtificialSweeteners, may vary by market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsArtificialSweeteners Context triple: [Pipeline Punch, containsArtificialSweeteners, may vary by market]
-
A.
containsSweeteners
Indicates that something includes one or more sweetening substances as part of its composition or contents.
-
B.
containsArtificialFlavors
Indicates that one entity includes or is made with artificial flavoring substances.
-
C.
containsArtificialPreservatives
Indicates that something includes one or more non-natural chemical substances added to extend shelf life or maintain qualities like flavor, color, or texture.
-
D.
containsSugarAlcohols
Indicates that the item includes one or more sugar alcohol compounds as part of its composition.
-
E.
isSugarFree
Indicates that something does not contain sugar or has been formulated without added sugar.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: April 27, 2026, 3:11 p.m.