Triple
T1148883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirandese language |
E23629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Astur-Leonese language |
C6376
|
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: Astur-Leonese language Context triple: [Mirandese language, instanceOf, Astur-Leonese language]
-
A.
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).
-
B.
Occitan dialect
An Occitan dialect is a regional variety of the Occitan language, characterized by distinct phonological, lexical, and grammatical features shaped by local history and geography within southern France and neighboring areas.
-
C.
Oïl language
An Oïl language is any of a group of closely related Romance languages and dialects historically spoken in northern France, Belgium, and the Channel Islands, characterized by the use of "oïl" (modern "oui") for "yes."
-
D.
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).
-
E.
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.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.