Triple
T25852156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the District of Vechta |
E651239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | symbol of administrative district |
C27345
|
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: symbol of administrative district Context triple: [Coat of arms of the District of Vechta, instanceOf, symbol of administrative district]
-
A.
administrativeDistrictName
The administrativeDistrictName class represents the official name assigned to a specific administrative district within a governmental or organizational territorial hierarchy.
-
B.
regional emblem
chosen
A regional emblem is a symbolic design or insignia that visually represents the identity, heritage, and distinguishing characteristics of a specific geographic region.
-
C.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
E.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:59 a.m.