Triple

T5688258
Position Surface form Disambiguated ID Type / Status
Subject Coat of arms of Estonia E125364 entity
Predicate tinctureOfLions P23235 FINISHED
Object Azure 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: Azure | Statement: [Coat of arms of Estonia, tinctureOfLions, Azure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tinctureOfLions
Context triple: [Coat of arms of Estonia, tinctureOfLions, Azure]
  • A. tinctureOfLion
    Indicates a relationship where something is a medicinal or alchemical preparation (a “tincture”) derived from or associated with a lion.
  • B. lionTincture chosen
    Indicates a heraldic relationship where a lion is depicted in a specific color or pattern (tincture) on a coat of arms or shield.
  • C. tressureTincture
    Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
  • D. tinctureOfTongueAndClaws
    Indicates a condition or effect in which both speech (tongue) and physical attacks (claws) are imbued with a special, often magical or poisonous, potency.
  • E. tinctureOfField
    Indicates that one entity is a tincture (medicinal extract or solution) derived from, based on, or primarily composed of another entity representing a field or source material.
  • 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_69c0082a884c8190a79001bae658941f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0248751bc8190b12aaa42d1ef17e3 completed March 22, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69c021be59088190a81c880957f666ab completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:44 p.m.