Triple
T6181298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Diocese of Derby |
E137947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical heraldic achievement |
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: ecclesiastical heraldic achievement Context triple: [Arms of the Diocese of Derby, instanceOf, ecclesiastical heraldic achievement]
-
A.
heraldic achievement
A heraldic achievement is the complete display of a coat of arms, including the shield, helm, crest, mantling, supporters, motto, and other accompanying elements arranged according to heraldic tradition.
-
B.
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.
-
C.
heraldic office
A heraldic office is an official institution or position responsible for designing, granting, recording, and regulating coats of arms and other heraldic symbols.
-
D.
heraldic authority
A heraldic authority is an official body or office responsible for granting, regulating, and recording coats of arms and other heraldic insignia within a particular jurisdiction.
-
E.
heraldic seal
A heraldic seal is an emblematic design, often bearing a coat of arms or symbolic imagery, used to authenticate documents and signify authority, lineage, or identity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:18 p.m.