Triple
T3831102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vlaheşte |
E91012
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Megleno-Romanian language |
C4907
|
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: Megleno-Romanian language Context triple: [vlaheşte, instanceOf, Megleno-Romanian language]
-
A.
Vlach language
The Vlach language is a Romance language or group of dialects spoken by Vlach communities in the Balkans, characterized by strong influence from surrounding Slavic, Greek, and Albanian languages.
-
B.
Eastern Romance language
chosen
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
C.
Gallo-Italic language
A Gallo-Italic language is a member of a group of Romance languages spoken primarily in northern Italy and parts of Switzerland, characterized by features intermediate between Gallo-Romance (like French) and Italo-Romance (like standard Italian).
-
D.
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.
-
E.
Anatolian language
An Anatolian language is any member of an extinct branch of the Indo-European language family once spoken in ancient Anatolia (modern-day Turkey), including languages such as Hittite, Luwian, and Lycian.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.