Triple
T22205397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religious Support Office |
E548792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army 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: U.S. Army chaplaincy organization Context triple: [Religious Support Office, instanceOf, U.S. Army chaplaincy organization]
-
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.
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.
-
C.
chaplaincy organization
chosen
A chaplaincy organization is an entity that provides spiritual care, counseling, and religious services to individuals within institutions such as hospitals, prisons, the military, schools, or workplaces.
-
D.
United States Army service component command
A United States Army service component command is the Army organization assigned to support, integrate, and provide Army forces to a specific unified combatant command, serving as its primary Army headquarters for planning and operations.
-
E.
U.S. Army institution
The U.S. Army institution is the formal organizational structure, culture, and governing framework that defines, supports, and regulates the United States Army’s missions, personnel, doctrine, and operations.
- 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.