Triple

T30181466
Position Surface form Disambiguated ID Type / Status
Subject Swiss Vice-Consul in Budapest E767211 entity
Predicate instanceOf P0 FINISHED
Object consular position C36375 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: consular position
Context triple: [Swiss Vice-Consul in Budapest, instanceOf, consular position]
  • A. consular authority chosen
    A consular authority is an official body or officer of a state, stationed in a foreign country, responsible for protecting the interests and assisting the citizens of its home state, as well as facilitating legal, administrative, and diplomatic functions related to travel, trade, and civil status.
  • B. diplomatic official
    A diplomatic official is a government-appointed representative who manages and promotes their nation's political, economic, and cultural interests in foreign states or international organizations.
  • C. chancellery position
    A chancellery position is an official role within a governmental or institutional chancellery responsible for high-level administrative, legal, or executive functions supporting the head of the organization.
  • D. diplomatic position
    A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
  • E. diplomatic service
    The diplomatic service is a governmental body of professional diplomats and support staff responsible for managing a nation's foreign relations, representing its interests abroad, and conducting negotiations with other states and international organizations.
  • F. None of above.

Provenance (1 batch)

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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:26 p.m.