Triple
T2662574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Utrecht |
E54758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Metropolitan see |
C7197
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Metropolitan see Context triple: [Roman Catholic Archdiocese of Utrecht, instanceOf, Metropolitan see]
-
A.
metropolitan see
chosen
A metropolitan see is the principal diocese of an ecclesiastical province, headed by a metropolitan bishop or archbishop who has limited supervisory authority over the other dioceses in that province.
-
B.
Anglican episcopal see
An Anglican episcopal see is the geographical area of jurisdiction and the associated office of a bishop within the Anglican Communion.
-
C.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
D.
Roman Catholic archdiocese
A Roman Catholic archdiocese is a primary ecclesiastical jurisdiction of the Catholic Church, led by an archbishop, that oversees a central territory and often has authority over neighboring dioceses within an ecclesiastical province.
-
E.
colonial city
A colonial city is an urban settlement established or significantly reshaped by a foreign colonial power, typically characterized by imposed administrative, economic, and cultural structures that reflect the colonizer’s interests more than those of the indigenous population.
- F. None of above.
Provenance (1 batch)
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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:53 p.m.