Triple
T17358656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarchal complex of the Romanian Orthodox Church |
E422010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical administrative center |
C6548
|
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: ecclesiastical administrative center Context triple: [Patriarchal complex of the Romanian Orthodox Church, instanceOf, ecclesiastical administrative center]
-
A.
religious administrative center
chosen
A religious administrative center is an institution or complex where the organizational, bureaucratic, and leadership functions of a religious community or denomination are coordinated and managed.
-
B.
ecclesiastical precinct
An ecclesiastical precinct is a defined area of land containing one or more religious buildings and associated structures, reserved for and organized around ecclesiastical functions and activities.
-
C.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
D.
Christian monastic center
A Christian monastic center is a religious community and physical complex where monks or nuns live under a shared rule of life devoted to prayer, worship, work, and spiritual formation.
-
E.
seat of traditional authority
A seat of traditional authority is a recognized position or institution whose legitimacy and power derive from long-established customs, cultural heritage, and historical continuity within a community or society.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.