Triple
T35785606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Israel |
E1034555
|
entity |
| Predicate | usesHeraldicShield |
P61212
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [coat of arms of Israel, usesHeraldicShield, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHeraldicShield Context triple: [coat of arms of Israel, usesHeraldicShield, yes]
-
A.
hasHeraldicShieldShape
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
-
B.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with another entity.
-
C.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
D.
hasHeraldicUse
chosen
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
E.
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.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22a1d2881909f51b6148da0a238 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.