Triple
T26453228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icacos Beach |
E665411
|
entity |
| Predicate | hasCommonTouristSeason |
P53625
|
FINISHED |
| Object | winter 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: winter months | Statement: [Icacos Beach, hasCommonTouristSeason, winter months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonTouristSeason Context triple: [Icacos Beach, hasCommonTouristSeason, winter months]
-
A.
isSeasonalAttraction
Indicates that an attraction is available or prominently featured only during specific seasons or times of the year.
-
B.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
C.
seasonalTourism
chosen
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
D.
hasIceBasedTourismSeason
Indicates that a location experiences a distinct tourism season specifically driven by ice-related conditions or activities.
-
E.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 12:07 a.m.