Triple
T5506995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdeaconry of Hastings |
E144464
|
entity |
| Predicate | hasTypeOfClergySupervised |
P3092
|
FINISHED |
| Object | parish priests |
—
|
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: parish priests | Statement: [Archdeaconry of Hastings, hasTypeOfClergySupervised, parish priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfClergySupervised Context triple: [Archdeaconry of Hastings, hasTypeOfClergySupervised, parish priests]
-
A.
hasClergyType
chosen
Indicates the specific category or role of clergy associated with an entity.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
D.
hasClergyRequirement
Indicates that a role, position, or activity requires the person involved to be a member of the clergy or to hold a specific clerical status.
-
E.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f47d2dc8190ad874be6902d8a4c |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.