Triple
T31071268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow city territory of Troitsky Administrative Okrug |
E791823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory of Moscow |
C38220
|
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: territory of Moscow Context triple: [Moscow city territory of Troitsky Administrative Okrug, instanceOf, territory of Moscow]
-
A.
federal territory of Russia
A federal territory of Russia is a special type of federal subject directly administered by the federal government, typically encompassing strategically important or unique areas with a distinct governance regime separate from surrounding regions.
-
B.
federal city of Russia
A federal city of Russia is a major urban locality that functions as a separate federal subject, holding the same administrative status as a region or republic and typically serving as a key political, economic, or cultural center.
-
C.
Cossack territory
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
-
D.
district of Russia
A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
-
E.
местность Москвы
chosen
Местность Москвы — это локализованный городской район столицы, характеризующийся исторически сложившейся застройкой, планировкой, социально-культурной средой и административной принадлежностью.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:01 p.m.