Triple
T31595423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pianoti |
E806205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arbëreshë community |
C26422
|
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: Arbëreshë community Context triple: [Pianoti, instanceOf, Arbëreshë community]
-
A.
Arbëreshë settlement
chosen
An Arbëreshë settlement is a community established by the Italo-Albanian (Arbëreshë) people, characterized by the preservation of their distinct Albanian language, Byzantine religious rites, and cultural traditions within Italy.
-
B.
Montenegrin tribe
A Montenegrin tribe is a traditional socio-territorial community in Montenegro, historically organized around kinship, shared customs, and a common geographic area, often functioning as a key unit of social, political, and military organization.
-
C.
Carpatho-Rusyn community
The Carpatho-Rusyn community is a stateless East Slavic ethnic group native to the Carpathian Mountain region, united by a distinct language, culture, and religious traditions that span across modern-day Ukraine, Slovakia, Poland, Romania, Hungary, and Serbia.
-
D.
person of Albanian origin
A person of Albanian origin is an individual whose ancestry, cultural heritage, or familial roots trace back to the Albanian people or the regions historically inhabited by them.
-
E.
Alevi community
The Alevi community is a culturally and religiously distinct group, primarily in Turkey and its diaspora, whose beliefs blend elements of Shia Islam, Sufism, and local traditions, emphasizing humanism, equality, and ritual practices centered on communal worship and music.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:30 p.m.