Triple
T17076471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprite Zero Sugar |
E414358
|
entity |
| Predicate | isPackagedFor |
P125761
|
FINISHED |
| Object | individual consumption |
—
|
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: individual consumption | Statement: [Sprite Zero Sugar, isPackagedFor, individual consumption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPackagedFor Context triple: [Sprite Zero Sugar, isPackagedFor, individual consumption]
-
A.
isPackagedForOfficeUse
Indicates that an item is packaged specifically for use in an office setting or environment.
-
B.
isPackageOf
Indicates that one entity is a package that contains, bundles, or delivers another entity.
-
C.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
D.
supportsPackagingModel
Indicates that one entity provides compatibility with or functionality for a particular packaging model used by another entity.
-
E.
hasPackageName
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.