Triple
T6146052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Diocese of Melbourne |
E137078
|
entity |
| Predicate | hasBishopRank |
P31297
|
FINISHED |
| Object | archbishop |
—
|
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: archbishop | Statement: [Anglican Diocese of Melbourne, hasBishopRank, archbishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBishopRank Context triple: [Anglican Diocese of Melbourne, hasBishopRank, archbishop]
-
A.
hasBishop
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.
hasPreviousBishop
Indicates that one bishop previously held the same episcopal position or office as another bishop.
-
D.
typeOfBishop
chosen
Indicates that one entity is a specific kind or category of bishop in relation to another entity.
-
E.
finalBishop
Indicates that an entity holds the position or role of the last or ultimate bishop in a given succession or context.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdd2dc0819080a4adf0cead3603 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.