Triple
T6181315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Diocese of Derby |
E137947
|
entity |
| Predicate | borderTincture |
P16378
|
FINISHED |
| Object | argent |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: argent | Statement: [Arms of the Diocese of Derby, borderTincture, argent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTincture Context triple: [Arms of the Diocese of Derby, borderTincture, argent]
-
A.
borderColor
chosen
Indicates the color that forms the boundary or outline of an entity.
-
B.
regionOfHeraldry
Indicates a relationship where a heraldic symbol, coat of arms, or emblem is associated with or belongs to a specific geographic or administrative region.
-
C.
heraldicCharge
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
D.
fieldForCrossTincture
Indicates that a field (background area) is designated to receive a cross tincture (coloring or pattern) in a heraldic design.
-
E.
coatOfArmsBackgroundColor
Indicates the background color used in a coat of arms design.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69c060fdf7ac8190a0e887907ec9a922 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.