Triple
T5880049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon State Ministry for Science, Culture and Tourism |
E130723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ministry of a German state |
C19067
|
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: ministry of a German state Context triple: [Saxon State Ministry for Science, Culture and Tourism, instanceOf, ministry of a German state]
-
A.
capital of a German state
A capital of a German state is the primary city where the government institutions and administrative bodies of one of Germany’s federal states are located.
-
B.
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.
-
C.
state of Germany
A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
-
D.
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.
-
E.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:57 p.m.