Triple
T36796025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Action in Italy |
E909183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lay Catholic organization |
C5849
|
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: lay Catholic organization Context triple: [Catholic Action in Italy, instanceOf, lay Catholic organization]
-
A.
Catholic organization
chosen
A Catholic organization is a structured group or institution that operates under the teachings, authority, and mission of the Catholic Church to promote religious, educational, charitable, or social objectives.
-
B.
religious auxiliary organization
A religious auxiliary organization is a subordinate group within a faith community that supports and extends the mission of the main religious body through specialized programs, services, or ministries.
-
C.
church organization
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
-
D.
Catholic Church
The Catholic Church is a worldwide Christian religious institution, led by the Pope, that traces its origins to Jesus Christ and the apostles and is characterized by a hierarchical structure, sacramental worship, and a unified body of doctrine.
-
E.
Roman Catholic mission network
A Roman Catholic mission network is an organized system of churches, religious orders, and agencies that coordinate evangelization, pastoral care, education, and charitable works to spread and sustain the Catholic faith across different regions and cultures.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.