Triple

T20073335
Position Surface form Disambiguated ID Type / Status
Subject Hungarian Crown E499792 entity
Predicate associatedWith P37 FINISHED
Object Hungarian royal chancery NE NERFINISHED

How this triple was built (3 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: Hungarian royal chancery | Statement: [Hungarian Crown, associatedWith, Hungarian royal chancery]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hungarian royal chancery
Context triple: [Hungarian Crown, associatedWith, Hungarian royal chancery]
  • A. Bohemian royal chancery
    The Bohemian royal chancery was the central medieval administrative office of the kings of Bohemia, responsible for producing and authenticating royal documents and managing official written communication of the realm.
  • B. National Archives of Hungary
    The National Archives of Hungary is the central institution responsible for preserving, organizing, and providing access to Hungary’s historical state documents and archival heritage.
  • C. Curia of Hungary
    The Curia of Hungary is the country’s supreme judicial authority, serving as the highest court of appeal and ensuring the uniform application of law across the Hungarian legal system.
  • D. Hungarian royal court
    The Hungarian royal court was the central political and ceremonial institution of the medieval Kingdom of Hungary, where the king and his entourage governed the realm and managed its aristocratic and ecclesiastical affairs.
  • E. House of Zápolya
    The House of Zápolya was a powerful Hungarian noble family of the late Middle Ages and early modern period, most notable for producing John Zápolya, a rival king of Hungary during the 16th century.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Hungarian royal chancery
Target entity description: The Hungarian royal chancery was the central administrative and documentary office of the medieval Kingdom of Hungary, responsible for drafting, issuing, and authenticating royal charters and official correspondence.
  • A. Bohemian royal chancery
    The Bohemian royal chancery was the central medieval administrative office of the kings of Bohemia, responsible for producing and authenticating royal documents and managing official written communication of the realm.
  • B. National Archives of Hungary
    The National Archives of Hungary is the central institution responsible for preserving, organizing, and providing access to Hungary’s historical state documents and archival heritage.
  • C. Curia of Hungary
    The Curia of Hungary is the country’s supreme judicial authority, serving as the highest court of appeal and ensuring the uniform application of law across the Hungarian legal system.
  • D. Hungarian royal court
    The Hungarian royal court was the central political and ceremonial institution of the medieval Kingdom of Hungary, where the king and his entourage governed the realm and managed its aristocratic and ecclesiastical affairs.
  • E. House of Zápolya
    The House of Zápolya was a powerful Hungarian noble family of the late Middle Ages and early modern period, most notable for producing John Zápolya, a rival king of Hungary during the 16th century.
  • F. None of above. chosen

Provenance (2 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e664392c748190a6cc472f80b8c74b completed April 20, 2026, 5:36 p.m.
Created at: April 11, 2026, 3:40 p.m.