Triple
T17077090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simply Orange Medium Pulp |
E414376
|
entity |
| Predicate | typicalUseOccasion |
P14787
|
FINISHED |
| Object | breakfast |
—
|
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: breakfast | Statement: [Simply Orange Medium Pulp, typicalUseOccasion, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseOccasion Context triple: [Simply Orange Medium Pulp, typicalUseOccasion, breakfast]
-
A.
usedOnOccasions
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
B.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
-
C.
suitableOccasion
Indicates that a particular occasion or context is appropriate or fitting for a given entity, action, or event.
-
D.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
E.
servingOccasion
chosen
Indicates the occasion, event, or context during which something (typically food or drink) is served.
- 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.