Triple
T632933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aromanian |
E15960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vlach language |
C4908
|
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: Vlach language Context triple: [Aromanian, instanceOf, Vlach language]
-
A.
Alpine language
Alpine language is a conceptual class representing any linguistic system that has evolved within or is predominantly used in mountainous Alpine regions, shaped by their geography, culture, and historical isolation.
-
B.
Oghuz language
The Oghuz language is a member of the Oghuz branch of the Turkic language family, historically spoken by the Oghuz Turks and forming the basis of several modern languages such as Turkish, Azerbaijani, and Turkmen.
-
C.
Celtic language
A Celtic language is a member of the Indo-European language family historically spoken in Western Europe, characterized by shared phonological, grammatical, and lexical features found in branches such as Goidelic (e.g., Irish, Scottish Gaelic) and Brittonic (e.g., Welsh, Breton).
-
D.
Greek language variety
A Greek language variety is a distinct form of the Greek language, characterized by specific phonological, grammatical, lexical, and pragmatic features associated with particular regions, communities, or social groups.
-
E.
Byzantine Greek
Byzantine Greek is the form of the Greek language used in the Eastern Roman (Byzantine) Empire from late antiquity to the fall of Constantinople, characterized by a mixture of classical, Koine, and emerging medieval features in grammar, vocabulary, and style.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.