Triple
T20463238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls Gap |
E501978
|
entity |
| Predicate | peakTouristPeriod |
P127382
|
FINISHED |
| Object | school holidays |
—
|
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: school holidays | Statement: [Halls Gap, peakTouristPeriod, school holidays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakTouristPeriod Context triple: [Halls Gap, peakTouristPeriod, school holidays]
-
A.
popularTimeToVisit
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
-
B.
hasPeakVisitationSeason
chosen
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
C.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a88374819087e7b97c83074d2c |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.