Triple
T13716965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignacy Posadzy |
E328925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co-founder of a religious congregation |
C13287
|
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: co-founder of a religious congregation Context triple: [Ignacy Posadzy, instanceOf, co-founder of a religious congregation]
-
A.
founder of religious organization
chosen
A founder of a religious organization is an individual who originates, establishes, and provides the initial doctrine, structure, and leadership for a new religious movement or institution.
-
B.
co-founder of the Society of Jesus
A co-founder of the Society of Jesus is an individual who, alongside Ignatius of Loyola and other early companions, played a foundational role in establishing the Jesuit religious order’s mission, structure, and spiritual charism.
-
C.
Seventh-day Adventist pioneer
A Seventh-day Adventist pioneer is an early leader, organizer, or influential member who helped establish, shape, and spread the beliefs, institutions, and global mission of the Seventh-day Adventist Church in the 19th and early 20th centuries.
-
D.
founder of a Buddhist school
A founder of a Buddhist school is an influential teacher or leader who establishes a distinct tradition or lineage within Buddhism by articulating its core doctrines, practices, and institutional forms.
-
E.
religious institute member
A religious institute member is an individual who has formally joined a religious community or order, committing to its spiritual life, rules, and mission, often through vows or promises.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.