Triple
T10870013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Union |
E256625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant military alliance |
C22718
|
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: Protestant military alliance Context triple: [Evangelical Union, instanceOf, Protestant military alliance]
-
A.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
B.
Protestant federation
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
-
C.
religious and political alliance
A religious and political alliance is a coalition in which faith-based groups and political actors formally or informally coordinate their agendas, resources, and influence to pursue shared ideological, social, or policy goals.
-
D.
political-military alliance
chosen
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
E.
anti-Bolshevik military coalition
An anti-Bolshevik military coalition is a temporary alliance of armed forces and political groups united to oppose, contain, or overthrow Bolshevik or communist regimes, typically during revolutionary or civil war contexts.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.