Triple
T2814371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Belarusian |
E54247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Belarusian language |
C10775
|
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: variety of Belarusian language Context triple: [Standard Belarusian, instanceOf, variety of Belarusian language]
-
A.
variety of the Albanian language
A variety of the Albanian language is a distinct, systematically patterned form of Albanian—such as a dialect, sociolect, or regional speech form—characterized by unique phonological, lexical, and grammatical features within the broader Albanian linguistic continuum.
-
B.
Baltic language
A Baltic language is a member of the Indo-European language family spoken primarily around the eastern coast of the Baltic Sea, characterized by conservative grammatical features and rich inflectional morphology.
-
C.
variety of the Irish language
A variety of the Irish language is a distinct regional or social form of Irish characterized by particular phonological, grammatical, and lexical features shared by its speakers.
-
D.
variety of the Greek language
A variety of the Greek language is a distinct form or dialect of Greek, characterized by specific phonological, grammatical, lexical, and pragmatic features used by a particular community or in a particular context.
-
E.
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.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:59 p.m.