Triple
T16170994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goryōkaku |
E392433
|
entity |
| Predicate | hasTouristSeasonPeak |
P118671
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Goryōkaku, hasTouristSeasonPeak, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristSeasonPeak Context triple: [Goryōkaku, hasTouristSeasonPeak, spring]
-
A.
isPeakVacationMonthIn
Indicates that a given month falls within the period of highest typical vacation activity in a specified location or context.
-
B.
isSeasonalAttraction
chosen
Indicates that an attraction is available or prominently featured only during specific seasons or times of the year.
-
C.
hasSeasonalRidershipPeak
Indicates that the ridership of an entity (such as a service or route) reaches its highest levels during specific seasons or times of the year.
-
D.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
-
E.
requiresReservationInPeakSeason
Indicates that the subject can only be accessed or used during peak season if a reservation has been made in advance.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.