Triple
T2108861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Moscow |
E42457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flag of a federal city of Russia |
C6985
|
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 federal city of Russia Context triple: [flag of Moscow, instanceOf, flag of a federal city of Russia]
-
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.
national flag
A national flag is a distinctive, officially sanctioned piece of cloth or emblem that symbolically represents a country’s identity, values, and sovereignty.
-
C.
regional flag
chosen
A regional flag is a symbolic banner that visually represents and distinguishes a specific geographic area, such as a state, province, or territory, through unique colors, patterns, and emblems.
-
D.
governmental flag
A governmental flag is an official banner used by a government to symbolize its authority, identity, and sovereignty in domestic and international contexts.
-
E.
constituent entity of Russia
A constituent entity of Russia is a primary administrative-territorial unit of the Russian Federation, such as a republic, krai, oblast, city of federal significance, autonomous okrug, or autonomous oblast, that possesses a defined degree of political and administrative autonomy under federal law.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:43 p.m.