Triple
T4539178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Liechtenstein |
E107484
|
entity |
| Predicate | escutcheonType |
P41231
|
FINISHED |
| Object | quarterly shield with inescutcheon |
—
|
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: quarterly shield with inescutcheon | Statement: [Coat of arms of Liechtenstein, escutcheonType, quarterly shield with inescutcheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escutcheonType Context triple: [Coat of arms of Liechtenstein, escutcheonType, quarterly shield with inescutcheon]
-
A.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
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.
hasHeraldicShieldShape
chosen
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
-
E.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57ba327c8190a7f12e14077b1fa7 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.