Triple
T36932825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian expedition to Egypt and Sudan |
E913529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian state-sponsored mission |
C62898
|
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 state-sponsored mission Context triple: [Prussian expedition to Egypt and Sudan, instanceOf, Prussian state-sponsored mission]
-
A.
Prussian state institution
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.
Prussian official
A Prussian official is a bureaucrat serving the Prussian state, characterized by strict discipline, legalistic administration, and loyalty to hierarchical authority.
-
C.
German overseas venture
A German overseas venture is an organized commercial or colonial enterprise initiated from Germany to establish economic, political, or cultural presence in foreign territories.
-
D.
Prussian colony
A Prussian colony is a territory politically and administratively controlled by the Kingdom of Prussia, typically acquired through conquest, diplomacy, or settlement, and governed to serve Prussian strategic, economic, and cultural interests.
-
E.
German state program
A German state program is a government-initiated and -funded scheme at the federal or state level designed to achieve specific public policy goals, such as economic development, social welfare, education, or environmental protection.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.