Triple
T8451551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian lozengy shield |
E199810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | symbol of Bavaria |
C20956
|
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 Bavaria Context triple: [Bavarian lozengy shield, instanceOf, symbol of Bavaria]
-
A.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
-
B.
European symbol
chosen
A European symbol is a sign, emblem, or motif that represents the cultural, political, historical, or social identity and values associated with Europe or its constituent nations.
-
C.
symbol of Brittany
A symbol of Brittany is a visual or emblematic representation, such as the ermine or the Gwenn-ha-du flag, that signifies the region’s cultural identity, heritage, and distinctiveness.
-
D.
symbol of Genoa
A symbol of Genoa represents an iconic emblem, landmark, or motif that distinctly identifies and evokes the cultural, historical, and maritime identity of the city of Genoa.
-
E.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:09 p.m.