Triple

T27461040
Position Surface form Disambiguated ID Type / Status
Subject Arms of the Diocese of Llandaff E692743 entity
Predicate heraldicType P58180 FINISHED
Object episcopal arms 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: episcopal arms | Statement: [Arms of the Diocese of Llandaff, heraldicType, episcopal arms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heraldicType
Context triple: [Arms of the Diocese of Llandaff, heraldicType, episcopal arms]
  • A. coatOfArmsType chosen
    Indicates the specific kind or category of coat of arms associated with an entity.
  • B. 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.
  • C. heraldicStatus
    Indicates the formal standing or classification of an entity within a heraldic system, such as its rank, legitimacy, or official recognition in heraldry.
  • D. 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.
  • E. heraldicName
    Indicates the formal name or designation assigned to a heraldic element (such as a coat of arms, charge, or symbol) within a heraldic system.
  • 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_69ef5207903881909427745cda05d27a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62df94be88190bcb43f8106c762dd completed May 2, 2026, 5:01 p.m.
PD Predicate disambiguation batch_69f623aaf40081909f947431424a1d55 completed May 2, 2026, 4:17 p.m.
Created at: April 27, 2026, 12:50 p.m.