Triple
T34939728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crown of shields |
E1007681
|
entity |
| Predicate | containsShield |
P202549
|
FINISHED |
| Object | historical coat of arms of Croatia proper |
—
|
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: historical coat of arms of Croatia proper | Statement: [crown of shields, containsShield, historical coat of arms of Croatia proper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsShield Context triple: [crown of shields, containsShield, historical coat of arms of Croatia proper]
-
A.
requiresShielding
Indicates that one entity must be protected or insulated from another entity or from certain conditions, typically for safety or proper functioning.
-
B.
hasShieldBearer
Indicates that one entity serves as the shield-bearing protector or defensive attendant for another entity.
-
C.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
D.
hasShieldCharge
Indicates that an entity performs or possesses the ability to execute a charging attack using a shield against another entity or target.
-
E.
shieldPresent
Indicates that a protective shield is currently active or available in the given context.
- F. None of above. chosen
Provenance (4 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_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a008eba6de8819083165152448f6071 |
completed | May 10, 2026, 1:57 p.m. |
Created at: May 3, 2026, 4 p.m.