Triple
T473816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuntsevo District |
E9016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of Moscow |
C740
|
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: administrative district of Moscow Context triple: [Kuntsevo District, instanceOf, administrative district of Moscow]
-
A.
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.
-
B.
metropolitan area
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
-
C.
federal district
A federal district is a distinct territorial unit under the direct jurisdiction of a national government, separate from any constituent state or province, typically established to house the nation's capital or serve special administrative purposes.
-
D.
Los Angeles City Council district
A Los Angeles City Council district is a geographically defined electoral area within the City of Los Angeles, each represented by a single councilmember responsible for local legislation, constituent services, and community advocacy.
-
E.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.