Triple
T14339841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic section of U.S. Embassy Vienna |
E355567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic section of an embassy |
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: economic section of an embassy Context triple: [Economic section of U.S. Embassy Vienna, instanceOf, economic section of an embassy]
-
A.
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.
-
B.
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.
-
C.
economic affairs ministry
The economic affairs ministry is a government department responsible for formulating and implementing policies that manage a nation's economic development, trade, industry, and financial stability.
-
D.
economic ministry
An economic ministry is a government department responsible for formulating and implementing national economic policy, including fiscal strategy, economic planning, and oversight of key economic sectors.
-
E.
diplomatic mission unit
chosen
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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:14 a.m.