Triple
T33719492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol Department of the Ministry of Foreign Affairs of Lithuania |
E863971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic protocol office |
C58799
|
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: diplomatic protocol office Context triple: [Protocol Department of the Ministry of Foreign Affairs of Lithuania, instanceOf, diplomatic protocol office]
-
A.
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.
-
B.
diplomatic convention
A diplomatic convention is a formal international agreement or treaty that establishes rules, procedures, or standards governing relations and conduct between states.
-
C.
foreign affairs office
chosen
A foreign affairs office is an organizational unit responsible for managing a government’s or institution’s interactions, negotiations, and relationships with foreign entities, including states, organizations, and individuals.
-
D.
diplomatic facility
A diplomatic facility is a building or complex used by a nation or international organization to conduct official diplomatic activities, house diplomatic staff, and provide consular services in a host country.
-
E.
set of diplomatic customs
A set of diplomatic customs is a collection of established, often unwritten, practices and protocols that guide the behavior, communication, and ceremonial interactions between states and their representatives.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.