Triple
T3638468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Department of Foreign Affairs |
E77127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swiss federal department |
C3428
|
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: Swiss federal department Context triple: [Federal Department of Foreign Affairs, instanceOf, Swiss federal department]
-
A.
department of France
A department of France is an administrative territorial division within the country, situated between the region and commune levels, responsible for local governance, public services, and implementation of national policies.
-
B.
federal ministerial office
A federal ministerial office is a governmental entity headed by a federal minister, responsible for developing, implementing, and overseeing policies and administrative functions within a specific national portfolio or sector.
-
C.
federal agency of Germany
A federal agency of Germany is a governmental body operating at the national level, responsible for implementing federal laws, policies, and administrative tasks within its designated area of competence.
-
D.
region of Switzerland
A region of Switzerland is a geographically defined area within the country characterized by shared cultural, linguistic, economic, or natural features that distinguish it from other parts of Switzerland.
-
E.
government ministry
chosen
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:24 p.m.