Triple
T2540420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Toronto |
E56370
|
entity |
| Predicate | hasAuxiliaryBishop |
P10284
|
FINISHED |
| Object | area bishops of the Diocese of Toronto |
—
|
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 bishops of the Diocese of Toronto | Statement: [Diocese of Toronto, hasAuxiliaryBishop, area bishops of the Diocese of Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuxiliaryBishop Context triple: [Diocese of Toronto, hasAuxiliaryBishop, area bishops of the Diocese of Toronto]
-
A.
hasBishop
chosen
Indicates that one entity possesses, is assigned, or is associated with a bishop in relation to another entity.
-
B.
hasNumberOfBishops
Indicates the relationship that specifies how many bishops are associated with a given entity.
-
C.
typeOfBishop
Indicates that one entity is a specific kind or category of bishop in relation to another entity.
-
D.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
E.
hasKing
Indicates that an entity possesses or is ruled by a king.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.