Triple
T1452036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Special Envoy for Sudan and South Sudan |
E31312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic mission unit |
C6686
|
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 mission unit Context triple: [Office of the Special Envoy for Sudan and South Sudan, instanceOf, diplomatic mission unit]
-
A.
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.
-
B.
diplomatic district
A diplomatic district is an urban area designated for embassies, consulates, international organizations, and related services that facilitate formal relations between states and global institutions.
-
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.
Japanese diplomatic mission
A Japanese diplomatic mission is an official government delegation, such as an embassy or consulate, representing Japan abroad to manage political, economic, cultural, and consular relations with the host country or international organization.
-
E.
foreign affairs ministry
A foreign affairs ministry is a government department responsible for managing a country's international relations, diplomacy, and representation abroad.
- F. None of above. chosen
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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.