Triple
T34939743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crown of shields |
E1007681
|
entity |
| Predicate | mainShieldBelow |
P28293
|
FINISHED |
| Object | red and white chequerboard shield of Croatia |
—
|
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: red and white chequerboard shield of Croatia | Statement: [crown of shields, mainShieldBelow, red and white chequerboard shield of Croatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainShieldBelow Context triple: [crown of shields, mainShieldBelow, red and white chequerboard shield of Croatia]
-
A.
hasShieldBearer
Indicates that one entity serves as the shield-bearing protector or defensive attendant for another entity.
-
B.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
C.
requiresShielding
Indicates that one entity must be protected or insulated from another entity or from certain conditions, typically for safety or proper functioning.
-
D.
traditionalShield
Indicates that an entity functions as or possesses a shield that is made or used according to traditional or culturally established practices.
-
E.
shieldPosition
chosen
Indicates the relative location or orientation of a shield with respect to the entity or context it is protecting.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.