Triple

T22533571
Position Surface form Disambiguated ID Type / Status
Subject ガーター勲章 E557101 entity
Predicate 紋章上の役割 P40770 FINISHED
Object 受章者の紋章にガーター帯を付加する権利を与える 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: 受章者の紋章にガーター帯を付加する権利を与える | Statement: [ガーター勲章, 紋章上の役割, 受章者の紋章にガーター帯を付加する権利を与える]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 紋章上の役割
Context triple: [ガーター勲章, 紋章上の役割, 受章者の紋章にガーター帯を付加する権利を与える]
  • A. hasHeraldicRole chosen
    Indicates that an entity holds or is assigned a specific role or function within a heraldic context (such as in coats of arms, armorial bearings, or heraldic ceremonies).
  • B. protectiveEmblemName
    Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
  • C. hasHeraldicMeaning
    Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
  • D. notableHerald
    Indicates that one entity is a herald (messenger or announcer) of particular significance or prominence in relation to another entity.
  • E. 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.
  • 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_69e11e57483c8190b0887c4f8ff26446 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ed88cf08190ae7e5b6bf9a80372 completed April 29, 2026, 1:28 a.m.
PD Predicate disambiguation batch_69e898c864148190a3f5feec7967d49c completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:51 p.m.