Triple
T29211165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Buddhist community |
E740549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical religious community |
C54781
|
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: historical religious community Context triple: [Tamil Buddhist community, instanceOf, historical religious community]
-
A.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
B.
religious settlement
A religious settlement is a community established and organized primarily around shared religious beliefs, practices, and institutions, often including places of worship and communal living arrangements.
-
C.
Christian ethnoreligious community
A Christian ethnoreligious community is a group whose shared Christian faith is tightly interwoven with a distinct ethnic identity, culture, and often common ancestry, forming a cohesive social and religious unit.
-
D.
Christian minority community
A Christian minority community is a group of Christians who live as a numerical or sociopolitical minority within a broader society where another religion or worldview is dominant, shaping their cultural, social, and religious experiences.
-
E.
religious heritage
Religious heritage is the collection of beliefs, practices, artifacts, sites, and traditions passed down through generations that embody the historical and cultural legacy of a faith community.
- F. None of above. chosen
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:11 p.m.