Triple
T22205399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religious Support Office |
E548792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military religious support office |
C13448
|
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: military religious support office Context triple: [Religious Support Office, instanceOf, military religious support office]
-
A.
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.
-
B.
military support organization
chosen
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
C.
United States Army chaplain
A United States Army chaplain is a commissioned military officer and ordained religious leader who provides spiritual care, moral guidance, and religious support to soldiers and their families in all operational environments.
-
D.
religious-military order
A religious-military order is an organized group that combines a shared religious or spiritual mission with a structured, often hierarchical, military function or code of conduct.
-
E.
military ordinariate
A military ordinariate is a specific ecclesiastical jurisdiction of the Catholic Church that provides pastoral care and spiritual services to members of the armed forces and their families, often across multiple dioceses or national boundaries.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.