Triple
T30544203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent Representative of the Netherlands to NATO |
E777366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | permanent representative position |
C34157
|
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: permanent representative position Context triple: [Permanent Representative of the Netherlands to NATO, instanceOf, permanent representative position]
-
A.
plenipotentiary representative
A plenipotentiary representative is an individual, typically a diplomat, who is fully authorized to act on behalf of a state or organization in negotiations and decision-making.
-
B.
senior United Nations position
A senior United Nations position is a high-level leadership role responsible for shaping and implementing UN policies, strategies, and operations across member states and agencies.
-
C.
diplomatic official
chosen
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.
-
D.
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.
-
E.
High Commissioner
A High Commissioner is a senior diplomatic representative, typically appointed between member states of a Commonwealth or international organization, who oversees political, administrative, and cooperative relations at the highest level.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:19 p.m.