Triple
T21084026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States diplomatic personnel |
E519441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic personnel |
C11653
|
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 personnel Context triple: [United States diplomatic personnel, instanceOf, diplomatic personnel]
-
A.
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.
-
B.
diplomatic delegation
A diplomatic delegation is an official group of representatives sent by a state or organization to another state or international body to conduct negotiations, foster relations, and represent its interests.
-
C.
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.
-
D.
Foreign Service personnel
chosen
Foreign Service personnel are government employees who represent and advance their nation’s interests abroad through diplomacy, consular services, policy reporting, and public engagement.
-
E.
diplomatic mission unit
A diplomatic mission unit is an organizational subdivision within a diplomatic mission responsible for carrying out specific functions such as political, economic, consular, cultural, or administrative activities in support of a state's foreign relations.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:49 p.m.