Triple
T34187056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinty Moore |
E876989
|
entity |
| Predicate | requiresRefrigerationBeforeOpening |
P125773
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Dinty Moore, requiresRefrigerationBeforeOpening, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresRefrigerationBeforeOpening Context triple: [Dinty Moore, requiresRefrigerationBeforeOpening, no]
-
A.
isRefrigeratedForSale
Indicates that an item is kept under refrigeration specifically for the purpose of being offered for sale.
-
B.
refrigerationRequirement
chosen
Indicates that the related item or substance must be kept at a specified refrigerated temperature or storage condition.
-
C.
refrigerated
Indicates that something is kept at a low temperature, typically in a refrigerator, to preserve its condition or freshness.
-
D.
requiresChillingTime
Indicates that an item, process, or preparation step must be kept at a low temperature for a specified period before it is ready for its next use or stage.
-
E.
isShelfStableBeforeOpening
Indicates that a product can be safely stored at room temperature without refrigeration until it is opened.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:55 a.m.