Triple

T2386816
Position Surface form Disambiguated ID Type / Status
Subject Russian heraldry E48841 entity
Predicate hasMottoTradition P38121 FINISHED
Object use of mottos is relatively rare compared to Western heraldry 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: use of mottos is relatively rare compared to Western heraldry | Statement: [Russian heraldry, hasMottoTradition, use of mottos is relatively rare compared to Western heraldry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMottoTradition
Context triple: [Russian heraldry, hasMottoTradition, use of mottos is relatively rare compared to Western heraldry]
  • A. hasMottoLikeFunction
    Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
  • B. usesMotto
    Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
  • C. hasMottoInText
    Indicates that an entity has a motto expressed in a specific textual form or wording.
  • D. mottoOriginalLanguage
    Indicates the language in which a motto was originally formulated or expressed.
  • E. mottoType
    Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
  • 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_69a88aa5f63081908d07fd302029fcbd completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc7d9d8148190bb8aa16fd4364aba completed March 7, 2026, 6:38 a.m.
PD Predicate disambiguation batch_69abc5a1b5748190b4cd8989700f4dd2 completed March 7, 2026, 6:28 a.m.
PDg Predicate description generation batch_69abc682d094819081a96ffb77c4c42a completed March 7, 2026, 6:32 a.m.
Created at: March 4, 2026, 7:57 p.m.