Triple
T4941668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Rotterdam |
E110949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical ecclesiastical territory |
C12509
|
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: historical ecclesiastical territory Context triple: [Bishopric of Rotterdam, instanceOf, historical ecclesiastical territory]
-
A.
ecclesiastical state
An ecclesiastical state is a political entity in which the government is directly controlled by religious authorities, often with a church leader serving as the head of state.
-
B.
Roman Catholic ecclesiastical province
A Roman Catholic ecclesiastical province is a territorial grouping of dioceses under the leadership of a metropolitan archbishop, established to coordinate pastoral activity and governance within a defined region of the Church.
-
C.
historical geographic entity
chosen
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
D.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.