Triple
T34939736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crown of shields |
E1007681
|
entity |
| Predicate | adoptedWithCurrentCoatOfArms |
P181876
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [crown of shields, adoptedWithCurrentCoatOfArms, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedWithCurrentCoatOfArms Context triple: [crown of shields, adoptedWithCurrentCoatOfArms, 1990]
-
A.
replacedOnCoatOfArmsBy
Indicates that one element or symbol on a coat of arms has been superseded and taken the place of by another element or symbol.
-
B.
mountOnCoatOfArms
Indicates that one element is depicted as a heraldic charge or figure placed upon a coat of arms.
-
C.
usesCoatOfArmsVariant
Indicates that an entity employs an alternative or modified version of a standard coat of arms rather than the primary or original design.
-
D.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
E.
hasCoatOfArmsDisplay
Indicates that an entity presents or exhibits a particular coat of arms in a visible or official manner.
- F. None of above. chosen
Provenance (4 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.