Triple
T35667810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Verdun |
E1030620
|
entity |
| Predicate | hasClericalProvinceRole |
P37644
|
FINISHED |
| Object | suffragan see |
—
|
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: suffragan see | Statement: [Diocese of Verdun, hasClericalProvinceRole, suffragan see]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalProvinceRole Context triple: [Diocese of Verdun, hasClericalProvinceRole, suffragan see]
-
A.
hasClericalProvince
chosen
Indicates that one ecclesiastical jurisdiction or entity is part of, or belongs to, a specific clerical (church) province.
-
B.
hasEcclesiasticalProvinceStatus
Indicates that an entity holds the official status or rank of an ecclesiastical province within a church’s organizational hierarchy.
-
C.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
D.
hasClericalAssociation
Indicates a relationship in which an entity is connected to or involved with clerical roles, duties, or religious office.
-
E.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:05 p.m.