Triple
T8783281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavic mythology |
E208984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic culture |
C25055
|
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: Slavic culture Context triple: [Slavic mythology, instanceOf, Slavic culture]
-
A.
Slavic people
Slavic people are an ethnolinguistic group of Indo-European origin whose diverse nations and cultures across Eastern, Central, and Southeastern Europe share related Slavic languages and historical roots.
-
B.
West Slavic people
West Slavic people are a subgroup of Slavic ethnic groups originating in Central Europe, primarily including Poles, Czechs, and Slovaks, who share related languages, cultural traditions, and historical development.
-
C.
West Slavic languages
West Slavic languages are a subgroup of the Slavic language family, including Polish, Czech, Slovak, and related languages, primarily spoken in Central Europe and characterized by shared phonological, grammatical, and lexical features.
-
D.
East Slavic polity
An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited and shaped by East Slavic peoples and their cultural, linguistic, and religious traditions.
-
E.
East Slavic polity
An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited, shaped, or governed by East Slavic peoples (Russians, Ukrainians, Belarusians, and related groups).
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:42 p.m.