Triple
T21139319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sievers' law |
E520888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-European sound law |
C1509
|
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: Indo-European sound law Context triple: [Sievers' law, instanceOf, Indo-European sound law]
-
A.
hypothesis in historical linguistics
A hypothesis in historical linguistics is a proposed explanation of how and why specific linguistic features or relationships between languages have changed over time, formulated to be tested against comparative and historical evidence.
-
B.
theory of Indo-European origins
The theory of Indo-European origins is a set of scholarly models and hypotheses that seek to explain where, when, and how the Proto-Indo-European language and its speakers emerged and dispersed to form the widespread Indo-European language family.
-
C.
historical sound change
chosen
Historical sound change is the systematic alteration of speech sounds in a language over time, resulting in predictable shifts in pronunciation patterns across generations.
-
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.
Indo-Europeanist
An Indo-Europeanist is a scholar who studies the Indo-European language family, including its historical development, comparative grammar, and reconstruction of its proto-language and related cultures.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.