Triple
T9670253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yevanic |
E234006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek-based Jewish dialect |
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: Greek-based Jewish dialect Context triple: [Yevanic, instanceOf, Greek-based Jewish dialect]
-
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.
Greek language variety
A Greek language variety is a distinct form of the Greek language, characterized by specific phonological, grammatical, lexical, and pragmatic features associated with particular regions, communities, or social groups.
-
C.
Hellenic language
The Hellenic language is a branch of the Indo-European language family encompassing Ancient, Medieval, and Modern Greek and their dialects, which have evolved over millennia in the Hellenic world.
-
D.
Byzantine Greek
Byzantine Greek is the form of the Greek language used in the Eastern Roman (Byzantine) Empire from late antiquity to the fall of Constantinople, characterized by a mixture of classical, Koine, and emerging medieval features in grammar, vocabulary, and style.
-
E.
Israelite
An Israelite is a member of the ancient Hebrew people, traditionally descended from the patriarch Jacob (also called Israel), who formed the tribes of Israel and developed the religious and cultural foundations of Judaism.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:15 p.m.