Triple
T28499772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunnan ham |
E721200
|
entity |
| Predicate | seasonalProduction |
P31603
|
FINISHED |
| Object | traditionally produced in cooler months |
—
|
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: traditionally produced in cooler months | Statement: [Yunnan ham, seasonalProduction, traditionally produced in cooler months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalProduction Context triple: [Yunnan ham, seasonalProduction, traditionally produced in cooler months]
-
A.
seasonalOrder
Indicates the temporal ordering of events or states according to their position within a recurring seasonal cycle.
-
B.
growingSeason
Indicates the period of the year during which growth or development actively occurs for the referenced entity.
-
C.
sowingSeason
Indicates the time period during which a particular crop is typically planted or sown.
-
D.
seasonCycle
Indicates a recurring pattern or sequence of seasons or seasonal phases that repeat over time.
-
E.
hasSeasonalNature
chosen
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 3:06 a.m.