Triple
T7984441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qin conquest of rival states |
E185654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war of unification |
C21976
|
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: war of unification Context triple: [Qin conquest of rival states, instanceOf, war of unification]
-
A.
Italian unification campaign
The Italian unification campaign refers to the 19th-century political and military efforts, led by figures like Cavour, Garibaldi, and Victor Emmanuel II, to consolidate the various independent states and territories of the Italian peninsula into a single nation-state of Italy.
-
B.
Romanian national unification
Romanian national unification is the historical and political process through which Romanian-speaking populations and territories sought to consolidate into a single nation-state, culminating in the formation and later expansion of modern Romania.
-
C.
legendary political unification
chosen
A legendary political unification is a mythic or semi-historical consolidation of diverse peoples or territories under a single authority, celebrated as a foundational moment of collective identity and enduring order.
-
D.
Italian Wars
The Italian Wars were a series of conflicts from 1494 to 1559 in which major European powers fought for control of the Italian peninsula, reshaping Renaissance politics, warfare, and diplomacy.
-
E.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:15 p.m.