Triple
T34055810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pastoral Ministries |
E873351
|
entity |
| Predicate | contextOfTraining |
P186401
|
FINISHED |
| Object | local church |
—
|
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: local church | Statement: [Pastoral Ministries, contextOfTraining, local church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextOfTraining Context triple: [Pastoral Ministries, contextOfTraining, local church]
-
A.
trainingIn
Indicates that one entity is undergoing or receiving training within the context, program, or domain specified by another entity.
-
B.
typicalTraining
Indicates that an entity commonly undergoes or is associated with a standard or usual form of training in relation to another entity or context.
-
C.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
D.
trainingUse
Indicates that something is used for training purposes, such as preparing, educating, or improving the skills or performance of an entity.
-
E.
trainingContribution
Indicates that an entity contributes to, participates in, or provides resources for a training process or activity.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 1, 2026, 1:52 a.m.