Triple
T19295973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snyder’s of Hanover Pretzel Pieces |
E482562
|
entity |
| Predicate | typicalShelfLife |
P28315
|
FINISHED |
| Object | several months unopened |
—
|
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: several months unopened | Statement: [Snyder’s of Hanover Pretzel Pieces, typicalShelfLife, several months unopened]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShelfLife Context triple: [Snyder’s of Hanover Pretzel Pieces, typicalShelfLife, several months unopened]
-
A.
shelfLife
chosen
Indicates the duration or conditions under which an item remains usable, effective, or safe before it is considered expired or unsuitable.
-
B.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
C.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
E.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8533c08190822a917ffa32812d |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.