Triple
T4265671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trentino dialect |
E96818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romance dialect |
C2433
|
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: Romance dialect Context triple: [Trentino dialect, instanceOf, Romance dialect]
-
A.
Romance language variety
A Romance language variety is a specific form or dialect of a Romance language, distinguished by its unique phonological, grammatical, and lexical features within the broader Romance language family.
-
B.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
C.
Jewish dialect
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.
-
D.
Scandinavian dialect
A Scandinavian dialect is a regional or social variety of a North Germanic language (such as Swedish, Danish, or Norwegian) characterized by distinct pronunciation, vocabulary, and grammar within the Scandinavian region.
-
E.
Romance lect
chosen
A Romance lect is a language variety—such as a dialect, sociolect, or closely related language—derived from Vulgar Latin and belonging to the Romance language family.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:07 p.m.