Triple
T38149750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Landkreis Weilheim-Schongau |
E952718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | symbol of Landkreis Weilheim-Schongau |
C64990
|
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 Landkreis Weilheim-Schongau Context triple: [coat of arms of Landkreis Weilheim-Schongau, instanceOf, symbol of Landkreis Weilheim-Schongau]
-
A.
symbol of Landkreis Garmisch-Partenkirchen
The symbol of Landkreis Garmisch-Partenkirchen is a heraldic emblem that visually represents the district’s identity, history, and regional characteristics within Bavaria.
-
B.
symbol of Oberhavel district
The symbol of Oberhavel district represents its regional identity and heritage, typically featuring distinctive local motifs that reflect its geography, history, and cultural character.
-
C.
symbol of Märkisch-Oderland
A symbol of Märkisch-Oderland represents the district’s identity, heritage, and regional characteristics through visual elements such as its coat of arms, flag, or emblem.
-
D.
symbol of Upper Austria
The symbol of Upper Austria is a conceptual class representing the official heraldic emblem and associated visual identifiers that signify the Austrian state of Upper Austria in cultural, historical, and administrative contexts.
-
E.
symbol of Kamenz
The symbol of Kamenz is a conceptual class representing the official emblem or coat of arms that visually identifies and symbolizes the town of Kamenz, encapsulating its historical, cultural, and civic identity.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.