Triple
T38635103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation of Jesus |
E937555
|
entity |
| Predicate | targetGroupOfMinistry |
P199998
|
FINISHED |
| Object | girls and young women |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: girls and young women | Statement: [Congregation of Jesus, targetGroupOfMinistry, girls and young women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetGroupOfMinistry Context triple: [Congregation of Jesus, targetGroupOfMinistry, girls and young women]
-
A.
typeOfMinistry
Indicates the specific category or kind of ministry that an entity belongs to or represents.
-
B.
scopeOfMinistry
Indicates the range of responsibilities, activities, or areas of authority covered by a particular ministry or ministerial role.
-
C.
methodOfMinistry
Indicates the specific way or approach through which ministry or religious service is carried out.
-
D.
coordinatesMinistriesFor
Indicates that one entity organizes, aligns, or manages the activities and efforts of multiple ministries to work together effectively.
-
E.
governmentalUnit
Indicates that one entity functions as a governmental or administrative unit in relation to another entity.
- F. None of above. chosen
Provenance (4 batches)
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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4:32 p.m.