Triple
T6030656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Diocese of Sydney |
E134292
|
entity |
| Predicate | hasSynodMembers |
P68858
|
FINISHED |
| Object | clergy |
—
|
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: clergy | Statement: [Anglican Diocese of Sydney, hasSynodMembers, clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSynodMembers Context triple: [Anglican Diocese of Sydney, hasSynodMembers, clergy]
-
A.
hasSynod
Indicates that an entity is associated with, governed by, or participates in a particular synod (a formal ecclesiastical council or assembly).
-
B.
hasSynodicalGovernment
Indicates that an entity is governed or administered through a synodical (council-based, typically ecclesiastical) system of decision-making.
-
C.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
D.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
-
E.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0561121708190a904e52aa3484988 |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:08 p.m.