Triple
T30044115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esto-Sadok |
E763397
|
entity |
| Predicate | winterSeason |
P168385
|
FINISHED |
| Object | typically from December to March |
—
|
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: typically from December to March | Statement: [Esto-Sadok, winterSeason, typically from December to March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winterSeason Context triple: [Esto-Sadok, winterSeason, typically from December to March]
-
A.
winterCharacteristic
Indicates a characteristic, feature, or quality that is specifically associated with or typical of winter.
-
B.
winterSession
Indicates that an event, course, or activity takes place during a designated winter academic or seasonal session.
-
C.
winterStatus
Indicates the condition, phase, or circumstances associated with the winter season for a given entity or context.
-
D.
winterTouristSeason
Indicates that the relationship or context occurs during the winter period when tourism activity is at its peak or is specifically targeted.
-
E.
winterFrequency
Indicates how often the related event, condition, or phenomenon occurs during the winter season.
- F. None of above. chosen
Provenance (4 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679db6f188190a8aaf451c8053bbb |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:53 p.m.