Triple
T29465888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Maarkedal |
E747378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flag of a municipality of Belgium |
C55645
|
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 municipality of Belgium Context triple: [Flag of Maarkedal, instanceOf, flag of a municipality of Belgium]
-
A.
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.
-
B.
flag of the Netherlands
A flag of the Netherlands is a rectangular tricolor banner consisting of three equal horizontal bands of red (top), white (middle), and blue (bottom) that symbolizes the Dutch nation.
-
C.
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.
-
D.
municipality of Belgium
A municipality of Belgium is the smallest administrative division in the country, governed by a local council and mayor, responsible for providing public services and local regulations within its defined territory.
-
E.
flag of a Crown dependency
A flag of a Crown dependency is the official banner representing a self-governing territory under the sovereignty of the British Crown, typically combining local symbols with elements reflecting its constitutional relationship to the United Kingdom.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:52 p.m.