Triple
T15853528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian consular network |
E384398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Prussian foreign service |
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: component of Prussian foreign service Context triple: [Prussian consular network, instanceOf, component of Prussian foreign service]
-
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.
Polish diplomat
A Polish diplomat is an official representative of Poland who conducts negotiations, fosters international relations, and protects Polish interests and citizens abroad.
-
C.
Bavarian civil servant
A Bavarian civil servant is a public-sector employee working within the administrative, legal, or regulatory institutions of the Free State of Bavaria, responsible for implementing laws, delivering public services, and upholding regional and federal regulations.
-
D.
Austrian civil servant
An Austrian civil servant is a government employee in Austria responsible for implementing public policies, administering state functions, and providing services to citizens in accordance with national laws and regulations.
-
E.
component of the Prussian Army
A component of the Prussian Army is an organizational subdivision—such as a regiment, corps, or specialized unit—responsible for specific military functions within the broader Prussian military structure.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.