Triple
T17585067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic–Oriental Orthodox dialogue history |
E428300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interchurch relations history |
C1073
|
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: interchurch relations history Context triple: [Catholic–Oriental Orthodox dialogue history, instanceOf, interchurch relations history]
-
A.
interfaith initiative
An interfaith initiative is a collaborative effort that brings together individuals or communities from different religious traditions to foster mutual understanding, respect, and cooperative action on shared concerns.
-
B.
interfaith center
An interfaith center is a dedicated space or organization that fosters dialogue, understanding, and collaboration among people of diverse religious and spiritual traditions.
-
C.
historical relationship
chosen
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
D.
ecumenical organization
An ecumenical organization is a group or body that promotes cooperation, dialogue, and unity among different Christian denominations while respecting their distinct traditions and beliefs.
-
E.
agreement between state and church
An agreement between state and church is a formal arrangement that defines the rights, responsibilities, and mutual relations between governmental authorities and religious institutions.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.