Triple
T1366093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Diocese of Connecticut |
E30006
|
entity |
| Predicate | overseesMinistryType |
P12182
|
FINISHED |
| Object | congregational ministry |
—
|
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: congregational ministry | Statement: [Episcopal Diocese of Connecticut, overseesMinistryType, congregational ministry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesMinistryType Context triple: [Episcopal Diocese of Connecticut, overseesMinistryType, congregational ministry]
-
A.
typeOfMinistry
chosen
Indicates the specific category or kind of ministry that an entity belongs to or represents.
-
B.
ministry
Indicates that an entity serves as a governmental ministry responsible for specific public functions or policy areas in relation to another entity.
-
C.
numberOfMinistries
Indicates the total count of ministries associated with or belonging to a given entity.
-
D.
formedAsMinistry
Indicates that an organization or body was created or established in the form of a ministry.
-
E.
hasMediaMinistry
Indicates that an entity operates, oversees, or is associated with a ministry or department responsible for media-related affairs.
- F. None of above.
Provenance (3 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d1d15481909d58b6fd8aa2e585 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.