Triple
T231846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal coat of arms of the United Kingdom (1801–1816) |
E4427
|
entity |
| Predicate | hasCrest |
P1617
|
FINISHED |
| Object | lion statant guardant crowned |
—
|
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: lion statant guardant crowned | Statement: [Royal coat of arms of the United Kingdom (1801–1816), hasCrest, lion statant guardant crowned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrest Context triple: [Royal coat of arms of the United Kingdom (1801–1816), hasCrest, lion statant guardant crowned]
-
A.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
B.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
C.
hasTypeOfInsignia
chosen
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
hasTrophyForm
Indicates that one entity exists in, or is characterized by, a special trophy-like form or version of another entity.
-
E.
hasPlume
Indicates that an entity possesses or exhibits a plume, such as a feathered tuft, spray, or column-like emission.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.