Triple
T31991642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanteletar tradition |
E816888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Finnish folk poetry tradition |
C32838
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Finnish folk poetry tradition Context triple: [Kanteletar tradition, instanceOf, Finnish folk poetry tradition]
-
A.
Nordic tradition
Nordic tradition encompasses the customs, beliefs, rituals, and cultural practices that have developed over centuries in the Nordic countries, shaped by their history, mythology, climate, and social values.
-
B.
Finnish dialect
A Finnish dialect is a regional or social variety of the Finnish language characterized by distinct pronunciation, vocabulary, and grammatical features that differ from the standardized form and other dialects.
-
C.
Finnish observance
A Finnish observance is a culturally or historically significant day, event, or practice recognized in Finland, often marked by specific traditions, ceremonies, or public awareness activities.
-
D.
episode in Finnish mythology
An episode in Finnish mythology is a distinct narrative unit or event within the broader mythic tradition of Finland, often featuring specific deities, heroes, or supernatural occurrences that convey cultural values and cosmological beliefs.
-
E.
regional folk tradition
chosen
A regional folk tradition is a set of locally rooted customs, stories, practices, and expressions passed down through generations that reflect the shared history, values, and identity of a specific geographic community.
- F. None of above.
Provenance (1 batch)
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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:13 a.m.