Triple
T20617370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imatrankoski rapids |
E506601
|
entity |
| Predicate | tourismStartPeriod |
P140799
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Imatrankoski rapids, tourismStartPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismStartPeriod Context triple: [Imatrankoski rapids, tourismStartPeriod, 18th century]
-
A.
touristServicesResumedYear
Indicates the year in which tourist services that were previously halted or disrupted began operating again.
-
B.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
C.
beganDiversificationIntoTourism
Indicates that an entity started expanding its activities or operations into the tourism sector from a certain point in time.
-
D.
tourismBoom
Indicates a rapid and significant increase in tourism activity, such as visitor numbers, spending, or development, within a particular place or period.
-
E.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
- F. None of above. chosen
Provenance (4 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadd30b88190af3a05527ad5ac64 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.