Triple
T28790065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audience with Negus of Abyssinia |
E726926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interfaith encounter |
C4762
|
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: interfaith encounter Context triple: [Audience with Negus of Abyssinia, instanceOf, interfaith encounter]
-
A.
interfaith initiative
chosen
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.
inter-Orthodox meeting
An inter-Orthodox meeting is a formal gathering of representatives from various autocephalous and autonomous Orthodox Churches to discuss, coordinate, and address common theological, pastoral, and administrative concerns within the Orthodox Christian world.
-
D.
theological dialogue
A theological dialogue is a structured conversational exchange in which participants explore, question, and interpret religious beliefs, doctrines, and experiences in pursuit of deeper understanding or truth.
-
E.
ecumenical conference
An ecumenical conference is a formal gathering of representatives from different Christian denominations, and sometimes other faiths, convened to discuss theological issues, promote unity, and coordinate cooperative action.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:23 a.m.