Triple

T16593988
Position Surface form Disambiguated ID Type / Status
Subject Richmond Herald of Arms in Ordinary E403159 entity
Predicate coatOfArmsAuthorityFor P18620 FINISHED
Object individuals in England 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: individuals in England | Statement: [Richmond Herald of Arms in Ordinary, coatOfArmsAuthorityFor, individuals in England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coatOfArmsAuthorityFor
Context triple: [Richmond Herald of Arms in Ordinary, coatOfArmsAuthorityFor, individuals in England]
  • A. governingHeraldicAuthority
    Indicates the official heraldic body or authority that has jurisdiction over, regulates, or grants the heraldic item in question.
  • B. scopeOfHeraldicAuthority chosen
    Indicates the extent or jurisdiction within which a heraldic authority is empowered to grant, regulate, or oversee coats of arms and related heraldic matters.
  • C. coatOfArms
    Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
  • D. designerOfCoatOfArms
    Indicates that one entity is the creator or designer responsible for the coat of arms associated with another entity.
  • E. coatOfArmsType
    Indicates the specific kind or category of coat of arms associated with an 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_69d883880d0c81908b5fcd454e767b60 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d70ad008190bba0901bf3c7089f completed April 18, 2026, 10:31 a.m.
PD Predicate disambiguation batch_69e296a7d9d0819088555bca6c936e79 completed April 17, 2026, 8:23 p.m.
Created at: April 10, 2026, 5:16 a.m.