Triple
T31858899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romaniote Greek |
E813268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish language variety |
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: Jewish language variety Context triple: [Romaniote Greek, instanceOf, Jewish language variety]
-
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.
Karaim language variety
A Karaim language variety is a specific regional or social form of the Karaim Turkic language, distinguished by its unique phonological, lexical, and grammatical features within the Karaim-speaking community.
-
C.
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.
-
D.
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.
-
E.
Yiddish-language work
A Yiddish-language work is any creative, scholarly, or informational piece—such as literature, theater, film, music, or academic writing—produced primarily in the Yiddish 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:52 p.m.