Triple
T4635691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Trinity Cathedral of Tbilisi |
E101524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian Orthodox cathedral |
C3174
|
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: Georgian Orthodox cathedral Context triple: [Holy Trinity Cathedral of Tbilisi, instanceOf, Georgian Orthodox cathedral]
-
A.
Georgian church building
A Georgian church building is a Christian place of worship constructed or used during the Georgian era (1714–1830/37), typically characterized by balanced classical proportions, restrained ornamentation, and often brick or stone facades reflecting the architectural tastes of that period.
-
B.
Catholic cathedral
A Catholic cathedral is a large, often architecturally grand church that serves as the central place of worship and administrative seat (cathedra) of a bishop within a Catholic diocese.
-
C.
cathedral church
chosen
A cathedral church is a principal Christian church that serves as the central place of worship and administrative seat of a bishop within a diocese.
-
D.
Roman Catholic cathedral
A Roman Catholic cathedral is a principal church within a diocese that serves as the bishop’s official seat and central place of worship, often distinguished by its significant architectural, historical, and liturgical importance.
-
E.
Russian Orthodox church
A Russian Orthodox church is a Christian religious building belonging to the Russian Orthodox tradition, characterized by its distinctive onion domes, iconostasis, and liturgical practices rooted in Eastern Orthodoxy.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.