Triple
T8269212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Єзуїтський колегіум у Луцьку |
E193379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | історичний архітектурний комплекс |
C2724
|
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: історичний архітектурний комплекс Context triple: [Єзуїтський колегіум у Луцьку, instanceOf, історичний архітектурний комплекс]
-
A.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
B.
Roman-Byzantine archaeological complex
A Roman-Byzantine archaeological complex is an integrated site containing architectural remains, artifacts, and stratified layers that document the transition and continuity between Roman and Byzantine periods in a specific region.
-
C.
architectural ensemble
chosen
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
D.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
E.
ancient guesthouse complex
An ancient guesthouse complex is a historical lodging facility composed of multiple interconnected structures and courtyards designed to accommodate travelers, provide communal services, and support trade or pilgrimage along important routes.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:50 p.m.