Triple
T33644699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resuk language |
E861926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lesser-known language variety |
C58390
|
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: lesser-known language variety Context triple: [Resuk language, instanceOf, lesser-known language variety]
-
A.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
-
B.
Indigenous language variety
An Indigenous language variety is a distinct form or dialect of a language traditionally spoken by an Indigenous community, reflecting its unique cultural, historical, and social practices.
-
C.
Semai language variety
A Semai language variety is a specific form or dialect of the Semai language, distinguished by its unique phonological, lexical, or grammatical features used by a particular Semai-speaking community.
-
D.
regional variety of the Pamona language
A regional variety of the Pamona language is a geographically or socially defined form of Pamona characterized by distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Pamona varieties.
-
E.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.