Triple
T17077076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simply Orange Pulp Free |
E414375
|
entity |
| Predicate | refrigeratedProduct |
P111436
|
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: [Simply Orange Pulp Free, refrigeratedProduct, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refrigeratedProduct Context triple: [Simply Orange Pulp Free, refrigeratedProduct, true]
-
A.
isRefrigeratedForSale
chosen
Indicates that an item is kept under refrigeration specifically for the purpose of being offered for sale.
-
B.
isProcessedFood
Indicates that a food item has been altered from its natural state through industrial or mechanical methods such as refining, adding ingredients, or preserving.
-
C.
notableMeatProduct
Indicates that one entity is a meat-based product that is especially prominent, well-known, or significant in relation to the other entity.
-
D.
isNonFoodProduct
Indicates that the referenced item is classified as a product that is not intended for consumption as food.
-
E.
storesFood
Indicates that one entity keeps or holds food items for future use or consumption.
- 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_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. |
Created at: April 10, 2026, 5:34 a.m.