Triple
T32301532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artillery Department |
E825251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian government agency |
C22131
|
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: Prussian government agency Context triple: [Artillery Department, instanceOf, Prussian government agency]
-
A.
Prussian state institution
chosen
A Prussian state institution is a formal governmental body or organization established by the Kingdom of Prussia to administer public affairs, implement state policies, and maintain social order within its territories.
-
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.
government agency of Bavaria
A government agency of Bavaria is an official public institution established by the Free State of Bavaria to implement laws, deliver administrative services, and support policy execution within its jurisdiction.
-
D.
federal body of Germany
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.
-
E.
government agency of Poland
A government agency of Poland is an official public institution established by the Polish state to perform specific administrative, regulatory, or service functions on behalf of the government.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:45 a.m.