Triple
T12786502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Barts |
E305640
|
entity |
| Predicate | patronTouristSeason |
P78489
|
FINISHED |
| Object | Christmas and New Year period |
—
|
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: Christmas and New Year period | Statement: [Saint Barts, patronTouristSeason, Christmas and New Year period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronTouristSeason Context triple: [Saint Barts, patronTouristSeason, Christmas and New Year period]
-
A.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
B.
typicalVisitorsPerSeason
Indicates the usual number of visitors associated with each season for a given entity or location.
-
C.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
D.
returnedAsSeasonalAttraction
Indicates that an entity that was previously unavailable has come back into use or display specifically as a limited-time or seasonal attraction.
-
E.
popularTimeToVisit
chosen
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5dbdb88190a1b06721ada51627 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.