Triple
T38023943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Diocese of Moosonee |
E948715
|
entity |
| Predicate | hasLaityBody |
P122480
|
FINISHED |
| Object | lay delegates |
—
|
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: lay delegates | Statement: [Anglican Diocese of Moosonee, hasLaityBody, lay delegates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaityBody Context triple: [Anglican Diocese of Moosonee, hasLaityBody, lay delegates]
-
A.
includesLaity
chosen
Indicates that a group, organization, or activity encompasses or involves laypersons rather than only clergy or religious professionals.
-
B.
hasViewOnLaity
Indicates that one entity holds a particular stance, opinion, or doctrinal position regarding the role or nature of laypeople.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
hasLayMinistry
Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
-
E.
hasLayGovernanceBody
Indicates that an organization is overseen or advised by a governance body composed primarily of non-clerical or non-executive lay members.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:20 p.m.