Triple
T28664081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAG |
E725541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Federal Labour Court 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 Labour Court of Germany Context triple: [BAG, instanceOf, Federal Labour Court of Germany]
-
A.
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.
-
B.
federal body of Germany
chosen
A federal body of Germany is an institution established by the German constitution or federal law that exercises legislative, executive, or judicial authority at the national level within the Federal Republic of Germany.
-
C.
Organisation in Deutschland
Eine Organisation in Deutschland ist eine strukturierte, rechtlich oder faktisch anerkannte Einheit von Personen und Ressourcen, die in Deutschland mit definierten Zielen, Regeln und Zuständigkeiten dauerhaft zusammenwirkt.
-
D.
district of Nuremberg
A district of Nuremberg is an administrative subdivision of the city that encompasses specific neighborhoods, local governance functions, and community services within its defined boundaries.
-
E.
committee of the Landtag of Bavaria
A committee of the Landtag of Bavaria is a specialized working body composed of selected members of the Bavarian state parliament that prepares decisions, drafts legislation, and conducts detailed deliberations on specific policy areas.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5 a.m.