Triple
T3932529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schweppes |
E90826
|
entity |
| Predicate | carbonationMethod |
P26165
|
FINISHED |
| Object | artificially carbonated |
—
|
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: artificially carbonated | Statement: [Schweppes, carbonationMethod, artificially carbonated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carbonationMethod Context triple: [Schweppes, carbonationMethod, artificially carbonated]
-
A.
carbonation
chosen
Indicates that a substance, typically a beverage, has been infused with carbon dioxide gas, resulting in bubbles or fizziness.
-
B.
fermentationMethod
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
-
C.
possibleFermentationVessel
Indicates that something can serve as a suitable container or environment in which fermentation may take place.
-
D.
primaryFermentationVessel
Indicates that one entity serves as the main container or vessel in which the primary fermentation process of another entity takes place.
-
E.
madeWithAlcohol
Indicates that something is created, prepared, or produced using alcohol as an ingredient or component.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedaaf3c881909539831bf3a8bf10 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.