Triple
T4502845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London area scheme |
E101262
|
entity |
| Predicate | areaBishopTitle |
P22835
|
FINISHED |
| Object | Area Bishop |
—
|
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: Area Bishop | Statement: [London area scheme, areaBishopTitle, Area Bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaBishopTitle Context triple: [London area scheme, areaBishopTitle, Area Bishop]
-
A.
diocesanBishopTitle
Indicates the formal ecclesiastical title held by a bishop who has jurisdiction over a diocese.
-
B.
typeOfBishop
Indicates that one entity is a specific kind or category of bishop in relation to another entity.
-
C.
currentArchbishopTitle
Indicates the official ecclesiastical title currently held by the person serving as archbishop of a given see or jurisdiction.
-
D.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
E.
suffraganBishopTitle
chosen
Indicates the ecclesiastical title held by a suffragan bishop in relation to their subordinate role within a diocese.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fb2bec8190b74b6a49d9475514 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.