Triple
T14574298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perhentian Islands |
E341998
|
entity |
| Predicate | touristHighSeason |
P78489
|
FINISHED |
| Object | June to August |
—
|
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: June to August | Statement: [Perhentian Islands, touristHighSeason, June to August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristHighSeason Context triple: [Perhentian Islands, touristHighSeason, June to August]
-
A.
popularTimeToVisit
chosen
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
-
B.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
C.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
-
D.
isPeakVacationMonthIn
Indicates that a given month falls within the period of highest typical vacation activity in a specified location or context.
-
E.
peakSeasonMonth
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f49d58819094fcd2a702e146cb |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.