Triple
T15887131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton University Office of Religious Life |
E385218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chaplaincy organization |
C36615
|
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: chaplaincy organization Context triple: [Princeton University Office of Religious Life, instanceOf, chaplaincy organization]
-
A.
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.
-
B.
military chaplain corps
A military chaplain corps is an organized body of clergy and religious support personnel within the armed forces that provides spiritual care, moral guidance, and religious services to service members and their families.
-
C.
religious organization committee
A religious organization committee is a structured group within a faith-based institution responsible for planning, coordinating, and overseeing specific religious, administrative, or community activities in alignment with the organization’s beliefs and goals.
-
D.
religious organization commission
A religious organization commission is a formal body established to oversee, regulate, or advise on the activities, governance, and compliance of religious institutions within a defined jurisdiction or denomination.
-
E.
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.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.