Triple
T32338887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Convention House of Deputies |
E826252
|
entity |
| Predicate | hasClergyDeputiesFrom |
P9815
|
FINISHED |
| Object | every diocese |
—
|
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: every diocese | Statement: [General Convention House of Deputies, hasClergyDeputiesFrom, every diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClergyDeputiesFrom Context triple: [General Convention House of Deputies, hasClergyDeputiesFrom, every diocese]
-
A.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
B.
hasNumberOfDeputies
Indicates the specific count of deputies associated with or assigned to an entity.
-
C.
hasDeputyHeads
Indicates that an entity has one or more individuals serving in subordinate leadership roles as deputy heads.
-
D.
hasClericalMember
Indicates that an entity includes or is associated with a member who performs clerical or administrative duties.
-
E.
hasNotableClergyman
Indicates that an entity is associated with a clergyman who is distinguished or notable in some recognized way.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 12:48 a.m.