Triple
T34670878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izmailovsky Kremlin |
E890375
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural and entertainment complex |
C725
|
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: cultural and entertainment complex Context triple: [Izmailovsky Kremlin, instanceOf, cultural and entertainment complex]
-
A.
entertainment complex
chosen
An entertainment complex is a large, multi-purpose facility that combines various leisure, recreational, and cultural attractions—such as cinemas, theaters, restaurants, gaming areas, and event spaces—within a single integrated venue.
-
B.
entertainment facility
An entertainment facility is a venue designed and equipped to provide recreational, cultural, or leisure activities to individuals or groups, such as theaters, amusement parks, sports arenas, or gaming centers.
-
C.
sports and education complex
A sports and education complex is a multifunctional facility that integrates athletic venues with academic and training spaces to support both physical development and educational activities.
-
D.
television studio complex
A television studio complex is a purpose-built facility that houses multiple studios, control rooms, production offices, technical infrastructure, and support spaces for creating, recording, and broadcasting television content.
-
E.
collection of cultural facilities
A collection of cultural facilities is an organized grouping of venues such as museums, theaters, galleries, and libraries that together provide spaces for cultural expression, preservation, and engagement.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.