Triple
T6943064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashot Mndoyants |
E160724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet architect |
C8569
|
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: Soviet architect Context triple: [Ashot Mndoyants, instanceOf, Soviet architect]
-
A.
Russian neoclassical architect
A Russian neoclassical architect is a designer of buildings in Russia who employs the principles of classical antiquity—such as symmetry, proportion, and the use of columns and pediments—adapted to local traditions and historical contexts from the late 18th to early 19th centuries.
-
B.
Soviet artist
chosen
A Soviet artist is a visual or performing creator who produced work within the Soviet Union’s political, social, and ideological framework, often navigating or embodying state-sanctioned styles such as Socialist Realism.
-
C.
Soviet artist
A Soviet artist is a creator who produced visual, literary, musical, or performing arts within the Soviet Union, often navigating or embodying state ideologies such as socialist realism while contributing to the cultural and political discourse of their time.
-
D.
Persian architect
A Persian architect is a designer who plans and creates buildings and spaces that reflect the aesthetic, cultural, and structural traditions of Persian architecture.
-
E.
Ottoman architect
An Ottoman architect is a designer and builder responsible for planning, engineering, and aesthetically shaping structures within the cultural, religious, and political context of the Ottoman Empire.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:28 p.m.