Triple
T412960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bath Abbey |
E9530
|
entity |
| Predicate | churchmanship |
P11202
|
FINISHED |
| Object | Anglican |
—
|
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: Anglican | Statement: [Bath Abbey, churchmanship, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchmanship Context triple: [Bath Abbey, churchmanship, Anglican]
-
A.
ecclesiasticalPolity
Indicates the form, structure, and governing system by which a religious or church organization is administered and its authority is distributed.
-
B.
churchPolity
Indicates the form, structure, and governing system by which a church or religious community is organized and administered.
-
C.
churchProvince
Indicates that one entity is an ecclesiastical province to which the other entity (typically a church jurisdiction or diocese) belongs or is administratively subordinate.
-
D.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
-
E.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.