Triple
T28553103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean cuisine |
E722938
|
entity |
| Predicate | seasonalEmphasis |
P31151
|
FINISHED |
| Object | fresh seasonal produce |
—
|
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: fresh seasonal produce | Statement: [Mediterranean cuisine, seasonalEmphasis, fresh seasonal produce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalEmphasis Context triple: [Mediterranean cuisine, seasonalEmphasis, fresh seasonal produce]
-
A.
hasSeasonalHighlight
chosen
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
B.
seasonalOrder
Indicates the temporal ordering of events or states according to their position within a recurring seasonal cycle.
-
C.
specialSeason
Indicates that an entity is associated with a particular season that is distinguished or treated differently from regular seasons (e.g., for events, offers, or conditions).
-
D.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
E.
famousSeasonalEvent
Indicates a recurring event that is widely recognized or celebrated during a particular season.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 3:44 a.m.