Triple
T793867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Slavonic |
E16974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic language |
C245
|
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 language Context triple: [Church Slavonic, instanceOf, Slavic language]
-
A.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
-
B.
Paleo-European language
A Paleo-European language is a hypothesized pre-Indo-European language or group of languages once spoken in prehistoric Europe, known primarily through substratum influences, place names, and limited archaeological and linguistic reconstruction.
-
C.
Indo-European language
chosen
An Indo-European language is a member of a large family of related languages spoken across Europe and parts of Asia, all descended from a common prehistoric ancestor known as Proto-Indo-European.
-
D.
Finnic language
A Finnic language is a member of the Uralic language family spoken primarily around the Baltic Sea region, including languages such as Finnish, Estonian, and Karelian, characterized by agglutinative morphology and vowel harmony.
-
E.
Dravidian language
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.