Triple
T6117181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilgrim Holiness Church |
E136386
|
entity |
| Predicate | laityInvolvement |
P11112
|
FINISHED |
| Object | strong lay participation |
—
|
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: strong lay participation | Statement: [Pilgrim Holiness Church, laityInvolvement, strong lay participation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laityInvolvement Context triple: [Pilgrim Holiness Church, laityInvolvement, strong lay participation]
-
A.
involvesClergy
Indicates that the situation, event, or action includes the participation or presence of clergy members.
-
B.
hasViewOnLaity
chosen
Indicates that one entity holds a particular stance, opinion, or doctrinal position regarding the role or nature of laypeople.
-
C.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
-
D.
nonParticipatingChurch
Indicates that a church is not taking part in a specified activity, program, event, or agreement.
-
E.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05beb4cfc8190ab67a5338ec59cea |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.