Triple
T19842709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettle Brand Backyard Barbeque potato chips |
E476775
|
entity |
| Predicate | isPackaged |
P137548
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kettle Brand Backyard Barbeque potato chips, isPackaged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPackaged Context triple: [Kettle Brand Backyard Barbeque potato chips, isPackaged, true]
-
A.
isPackagedFor
Indicates that one entity is prepared, contained, or wrapped specifically for use, sale, or distribution in connection with another entity.
-
B.
isPackagedForOfficeUse
Indicates that an item is packaged specifically for use in an office setting or environment.
-
C.
isPackageOf
Indicates that one entity is a package that contains, bundles, or delivers another entity.
-
D.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65806ea888190850421154238d91c |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.