Triple
T29153197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Lebanon |
E738966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian community in Lebanon |
C54692
|
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 Lebanon Context triple: [Catholic Church in Lebanon, instanceOf, Christian community in Lebanon]
-
A.
region of Lebanon
A region of Lebanon is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and physical features.
-
B.
Levantine community
A Levantine community is a social group rooted in the Eastern Mediterranean region (the Levant), characterized by shared historical, cultural, linguistic, and often religious ties that span modern national borders.
-
C.
Christian community in Asia Minor
A Christian community in Asia Minor is a group of believers in Jesus Christ living in the Roman provinces of western Anatolia, sharing a common faith, worship, and communal life shaped by early Christian teachings and local cultural contexts.
-
D.
Lebanese Maronite
A Lebanese Maronite is a member of the Maronite Catholic community originating from Lebanon, characterized by its Syriac Christian liturgical tradition, communion with the Roman Catholic Church, and significant cultural and historical influence in Lebanese society.
-
E.
neighborhood of Beirut
A neighborhood of Beirut is a distinct urban district within the city characterized by its own social fabric, architectural style, local commerce, and cultural or religious identity.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:43 a.m.