Triple
T666305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Coalition |
E12869
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coalition in the French Revolutionary Wars |
C458
|
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: coalition in the French Revolutionary Wars Context triple: [Second Coalition, instanceOf, coalition in the French Revolutionary Wars]
-
A.
coalition
chosen
A coalition is a temporary or long-term alliance of individuals, groups, or organizations that coordinate their resources and actions to achieve shared goals or exert collective influence.
-
B.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union authority.
-
C.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
D.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
E.
American Revolutionary War faction
An American Revolutionary War faction is a distinct political, military, or social group that aligned around specific loyalties, strategies, and interests during the American struggle for independence between 1775 and 1783.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.