Triple
T19353800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Selection Committee of Germany |
E484086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal body of Germany |
C41981
|
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: federal body of Germany Context triple: [Judicial Selection Committee of Germany, instanceOf, federal body of Germany]
-
A.
cooperative body of German federal states
A cooperative body of German federal states is an intergovernmental institution through which the Länder coordinate policies, negotiate common positions, and jointly represent their interests within Germany’s federal system.
-
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.
federal state of Germany
A federal state of Germany is a constituent political entity within the Federal Republic of Germany that possesses its own government, constitution, and legislative powers under the framework of the German federal system.
-
D.
German federal government
The German federal government is the central executive authority of the Federal Republic of Germany, consisting primarily of the Federal Chancellor and federal ministers, responsible for implementing laws and directing national policy.
-
E.
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.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:34 p.m.