Triple
T6993573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hancock, Massachusetts |
E162143
|
entity |
| Predicate | hasSeasonalTourismPeak |
P53625
|
FINISHED |
| Object | winter |
—
|
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 | Statement: [Hancock, Massachusetts, hasSeasonalTourismPeak, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalTourismPeak Context triple: [Hancock, Massachusetts, hasSeasonalTourismPeak, winter]
-
A.
seasonalTourism
chosen
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
B.
hasSeasonalMigration
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
-
C.
isPeakVacationMonthIn
Indicates that a given month falls within the period of highest typical vacation activity in a specified location or context.
-
D.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
E.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbeaa88c8190a49f8504c1793e1f |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.