Triple
T38556535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal arms of Charles II within a bordure compony argent and azure |
E925259
|
entity |
| Predicate | hasBordureTincture |
P124935
|
FINISHED |
| Object | argent and azure |
—
|
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 and azure | Statement: [Royal arms of Charles II within a bordure compony argent and azure, hasBordureTincture, argent and azure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBordureTincture Context triple: [Royal arms of Charles II within a bordure compony argent and azure, hasBordureTincture, argent and azure]
-
A.
tinctureOfBordure
chosen
Indicates that one element is depicted as a tincture (color or pattern) specifically applied to the bordure (border) of another element.
-
B.
bordureType
Indicates the specific style or pattern used for the border or edging of an item or area.
-
C.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
-
D.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
E.
hadBorder
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.