Triple
T30787226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Immaculate Conception, Moscow |
E783987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Moscow |
C57832
|
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: landmark in Moscow Context triple: [Cathedral of Immaculate Conception, Moscow, instanceOf, landmark in Moscow]
-
A.
building in Moscow
chosen
A building in Moscow is a constructed structure within the city’s urban environment, serving residential, commercial, governmental, or cultural functions and reflecting the architectural styles and historical layers of Russia’s capital.
-
B.
cultural heritage monument of regional significance in Moscow
A cultural heritage monument of regional significance in Moscow is an officially protected site, building, or object recognized by city authorities for its historical, architectural, or cultural value to the Moscow region.
-
C.
Moscow Monorail station
A Moscow Monorail station is a designated stop along the Moscow Monorail system where passengers can board, alight, and transfer between monorail trains and other modes of public transportation.
-
D.
местность Москвы
Местность Москвы — это локализованный городской район столицы, характеризующийся исторически сложившейся застройкой, планировкой, социально-культурной средой и административной принадлежностью.
-
E.
museum in Saint Petersburg
A museum in Saint Petersburg is a cultural institution that collects, preserves, researches, and exhibits artworks, historical artifacts, or scientific objects within the city of Saint Petersburg for public education and enrichment.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:41 p.m.