Triple
T1018018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Arms of England and Scotland quarterly |
E21975
|
entity |
| Predicate | languageOfBlazon |
P5036
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Royal Arms of England and Scotland quarterly, languageOfBlazon, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfBlazon Context triple: [Royal Arms of England and Scotland quarterly, languageOfBlazon, English]
-
A.
coatOfArmsMotto
Indicates the phrase or motto that appears on or is officially associated with a particular coat of arms.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
emblemLanguage
chosen
Indicates that an emblem (such as a symbol or logo) is associated with or presented in a particular language.
-
D.
heraldicTradition
Indicates a relationship where something belongs to, follows, or is characterized by a particular system or style of heraldic customs and practices.
-
E.
officialLanguageOnFlag
Indicates that a particular language is officially represented in the text or inscriptions displayed on a flag.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.