Triple
T9361258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Marathi |
E225280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marathi-based Jewish language |
C14735
|
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: Marathi-based Jewish language Context triple: [Judeo-Marathi, instanceOf, Marathi-based Jewish language]
-
A.
Jewish dialect
chosen
A Jewish dialect is a variety of a language shaped by the historical, religious, and cultural experiences of Jewish communities, often incorporating Hebrew or Aramaic elements and distinct phonological, lexical, and syntactic features.
-
B.
Gujarati dialect
A Gujarati dialect is a regional or social variety of the Gujarati language characterized by distinct phonological, lexical, and grammatical features used by specific communities within Gujarati-speaking regions.
-
C.
Gondi language variety
A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
-
D.
Marathi dialect
A Marathi dialect is a regional or social variety of the Marathi language characterized by distinct phonological, lexical, and syntactic features while remaining mutually intelligible with standard Marathi.
-
E.
regional variety of the Georgian language
A regional variety of the Georgian language is a geographically or socially localized form of Georgian characterized by distinct phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with the standard language.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:42 p.m.