Triple
T16768889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christians in Philippi |
E407538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian community in Europe |
C34881
|
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: Christian community in Europe Context triple: [Christians in Philippi, instanceOf, Christian community in Europe]
-
A.
Eastern Orthodox community
An Eastern Orthodox community is a group of faithful united in worship, doctrine, and sacramental life within the Eastern Orthodox Church, typically centered around a parish or local congregation and its clergy.
-
B.
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.
-
C.
Eurasian community
A Eurasian community is a social and cultural group formed by people, institutions, and networks that connect and integrate societies across Europe and Asia through shared interests, interactions, and identities.
-
D.
Christian minority community
chosen
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.
Anglican religious community
An Anglican religious community is a group of men or women within the Anglican tradition who live under a common rule of life, sharing prayer, worship, and service in a vowed or committed communal setting.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.