Triple
T5915743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Mirandese |
E131575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mirandese dialect |
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: Mirandese dialect Context triple: [Central Mirandese, instanceOf, Mirandese dialect]
-
A.
language of Portugal
The language of Portugal is European Portuguese, a Romance language derived from Latin and characterized by its distinct phonology, vocabulary, and grammar within the Lusophone world.
-
B.
Astur-Leonese language
chosen
The Astur-Leonese language is a Romance language continuum spoken primarily in Asturias, León, and surrounding regions of northwestern Spain, characterized by its own distinct phonological, lexical, and grammatical features separate from Spanish and Galician-Portuguese.
-
C.
variety of Portuguese
A variety of Portuguese is a distinct form of the Portuguese language characterized by specific phonological, lexical, syntactic, and pragmatic features associated with a particular geographic region, social group, or communicative context.
-
D.
variety of Portuguese language
A variety of Portuguese language is a regional or social form of Portuguese characterized by distinct phonological, lexical, and grammatical features shared by a specific speech community.
-
E.
Portuguese-based creole
A Portuguese-based creole is a stable, fully developed language that arose from prolonged contact between Portuguese and one or more other languages, incorporating Portuguese-derived vocabulary within a distinct grammatical and phonological system.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.