Triple

T30545553
Position Surface form Disambiguated ID Type / Status
Subject Coat of arms of Satakunta E777402 entity
Predicate heraldicAttitudeOfBear P37998 FINISHED
Object rampant 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: rampant | Statement: [Coat of arms of Satakunta, heraldicAttitudeOfBear, rampant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heraldicAttitudeOfBear
Context triple: [Coat of arms of Satakunta, heraldicAttitudeOfBear, rampant]
  • A. hasHeraldicAttitude chosen
    Indicates that an entity (typically an animal or figure in heraldry) is depicted with a specific standardized posture or stance in a coat of arms.
  • B. bearsSymbol
    Indicates that one entity carries, displays, or is marked with a particular symbol associated with it.
  • C. heraldicAspect
    Indicates a relationship where one entity serves as a heraldic feature, attribute, or component in the coat of arms or heraldic representation of another entity.
  • D. bears
    Indicates that one entity carries, supports, or endures the weight, burden, or responsibility of another entity or condition.
  • 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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6888fc28081908f26f1fed090f597 completed May 2, 2026, 11:28 p.m.
PD Predicate disambiguation batch_69f67e42d6688190b60e91d2c388c555 completed May 2, 2026, 10:44 p.m.
Created at: April 29, 2026, 8:19 p.m.