Triple
T31048802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanemuine |
E791199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in Estonian mythology |
C59727
|
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: character in Estonian mythology Context triple: [Vanemuine, instanceOf, character in Estonian mythology]
-
A.
figure in Finnish mythology
A figure in Finnish mythology is a supernatural or legendary being, deity, hero, or spirit that appears in Finland’s traditional stories, beliefs, and epic poetry such as the Kalevala.
-
B.
Finnish mythological figure
A Finnish mythological figure is a legendary being, deity, or hero from Finland’s traditional folklore and the national epic Kalevala, embodying natural forces, moral values, or cultural ideals.
-
C.
character in Irish mythology
A character in Irish mythology is a figure—divine, heroic, or supernatural—who appears in traditional Irish tales and legends, embodying cultural values, beliefs, and themes through their actions and relationships.
-
D.
object in Finnish mythology
An object in Finnish mythology is a tangible or symbolic item—such as a weapon, tool, artifact, or natural feature—endowed with mythic origin, supernatural power, or cultural significance within the Finnish mythological tradition.
-
E.
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.
- F. None of above. chosen
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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9 p.m.