Triple
T20916968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celerina |
E515096
|
entity |
| Predicate | secondaryTourismSeason |
P78276
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Celerina, secondaryTourismSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTourismSeason Context triple: [Celerina, secondaryTourismSeason, summer]
-
A.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
B.
summerTouristSeason
Indicates the period during summer when a place experiences increased tourist activity or visitation.
-
C.
secondaryVisitationSeason
chosen
Indicates a time period that serves as a secondary or less prominent season during which visits or visitation activity typically occurs.
-
D.
isSeasonalAttraction
Indicates that an attraction is available or prominently featured only during specific seasons or times of the year.
-
E.
winterTouristSeason
Indicates that the relationship or context occurs during the winter period when tourism activity is at its peak or is specifically targeted.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec635f4881909a560fb891100d8c |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.