Triple
T16432937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chester Herald of Arms in Ordinary |
E399112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | herald of arms in ordinary |
C4082
|
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: herald of arms in ordinary Context triple: [Chester Herald of Arms in Ordinary, instanceOf, herald of arms in ordinary]
-
A.
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.
-
B.
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.
-
C.
heraldic register
A heraldic register is an official record or database that documents and regulates coats of arms, crests, and other heraldic devices along with their authorized bearers.
-
D.
junior officer of arms
chosen
A junior officer of arms is a lower-ranking heraldic official who assists senior officers in managing coats of arms, ceremonial protocol, and genealogical records.
-
E.
heraldry tradition
Heraldry tradition is the historical system of designing, displaying, and regulating coats of arms and related symbols to represent lineage, authority, and identity across generations.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.