Triple
T37571464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit Conference of Asia Pacific |
E934698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jesuit conference |
C62848
|
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: Jesuit conference Context triple: [Jesuit Conference of Asia Pacific, instanceOf, Jesuit conference]
-
A.
Catholic bishops’ conference
A Catholic bishops’ conference is an official assembly of bishops from a particular country or region who collaborate to discuss, coordinate, and implement pastoral, liturgical, and doctrinal policies for the local Church in communion with the Holy See.
-
B.
rectors conference
A rectors conference is a formal assembly of university leaders (such as rectors, presidents, or chancellors) who meet to discuss, coordinate, and decide on shared policies, strategies, and issues affecting higher education institutions.
-
C.
Jesuit seminary
A Jesuit seminary is a religious educational institution where members of the Society of Jesus undergo spiritual, philosophical, and theological formation in preparation for priesthood and ministry.
-
D.
Jesuit college
A Jesuit college is a higher education institution founded and run by the Society of Jesus, emphasizing rigorous academics, spiritual formation, social justice, and service in the Catholic intellectual tradition.
-
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. 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.