Triple
T13637912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Prince-Bishopric of Hildesheim |
E325898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | symbol of an ecclesiastical principality |
C4451
|
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 an ecclesiastical principality Context triple: [Arms of the Prince-Bishopric of Hildesheim, instanceOf, symbol of an ecclesiastical principality]
-
A.
ecclesiastical heraldic emblem
chosen
An ecclesiastical heraldic emblem is a symbolic coat of arms or badge used by a church, cleric, or religious institution to represent its authority, identity, and spiritual mission within heraldic tradition.
-
B.
symbol of royal authority
A symbol of royal authority is an object, emblem, or regalia that visibly represents the sovereign’s legitimate power, status, and right to rule.
-
C.
symbol of monarchy
A symbol of monarchy is any emblem, object, or visual representation that signifies the authority, legitimacy, and continuity of a royal ruler or royal institution.
-
D.
symbol of church–state conflict
A symbol of church–state conflict represents the tensions, struggles, and power negotiations between religious institutions and governmental authorities over influence, authority, and societal control.
-
E.
organ of the Holy See
An organ of the Holy See is an official body, institution, or office that acts on behalf of the Holy See to exercise its spiritual, administrative, diplomatic, or judicial functions within the Catholic Church and in relations with states and international organizations.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.