Triple
T15286243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Proto-Slavic dialects |
E365407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stage of Proto-Slavic |
C1722
|
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: stage of Proto-Slavic Context triple: [West Proto-Slavic dialects, instanceOf, stage of Proto-Slavic]
-
A.
stage of the Czech language
A stage of the Czech language is a historically and linguistically distinct period in the development of Czech, characterized by specific phonological, grammatical, lexical, and orthographic features.
-
B.
Slavic dialect
A Slavic dialect is a regional or social variety of a Slavic language characterized by distinct phonological, grammatical, and lexical features that differentiate it from the standard language and other dialects.
-
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.
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.
-
E.
historical language stage
chosen
A historical language stage is a distinct, temporally bounded phase in the development of a language, characterized by relatively stable structural features and documented through historical evidence.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.