Triple
T32360935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Diocese of Innsbruck |
E826859
|
entity |
| Predicate | hasHeraldicFieldShape |
P41231
|
FINISHED |
| Object | shield-shaped escutcheon |
—
|
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: shield-shaped escutcheon | Statement: [Coat of arms of the Diocese of Innsbruck, hasHeraldicFieldShape, shield-shaped escutcheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldicFieldShape Context triple: [Coat of arms of the Diocese of Innsbruck, hasHeraldicFieldShape, shield-shaped escutcheon]
-
A.
hasHeraldicShieldShape
chosen
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
-
B.
hasHeraldicOrientation
Indicates the directional or positional orientation of a heraldic element within a coat of arms or similar heraldic context.
-
C.
hasHeraldicOrdinary
Indicates that an entity bears or includes a specific heraldic ordinary (a basic geometric figure) as part of its coat of arms or heraldic design.
-
D.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
E.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with another entity.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 12:49 a.m.