Triple
T30557977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Novocherkassk |
E777753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flag of a city in Russia |
C56281
|
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: flag of a city in Russia Context triple: [Flag of Novocherkassk, instanceOf, flag of a city in Russia]
-
A.
Soviet republic flag
A Soviet republic flag is a national or regional banner used by a constituent republic of the former Soviet Union, typically featuring a red field with communist symbols such as the hammer and sickle and localized emblems or inscriptions.
-
B.
flag of a city in Germany
A flag of a city in Germany is a distinctive piece of cloth bearing specific colors, patterns, and symbols officially adopted to represent and identify that municipality.
-
C.
flag of a city in the Netherlands
A flag of a city in the Netherlands is a distinctive rectangular banner that visually represents a specific Dutch municipality through unique combinations of colors, symbols, and patterns often rooted in local history and heraldry.
-
D.
city in Russia
A city in Russia is an urban locality within the Russian Federation that serves as a center of population, administration, economy, and culture, typically possessing municipal governance and infrastructure.
-
E.
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.
- F. None of above. chosen
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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:21 p.m.