Triple
T1315555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamasee War |
E28094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early 18th-century conflict |
C7387
|
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: early 18th-century conflict Context triple: [Yamasee War, instanceOf, early 18th-century conflict]
-
A.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
-
B.
event in the Seven Years' War
An event in the Seven Years' War is a specific historical occurrence—such as a battle, treaty, campaign, or political decision—that took place between 1756 and 1763 and significantly influenced the course or outcome of the global conflict.
-
C.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
D.
20th-century conflict
20th-century conflict encompasses the major wars, revolutions, and geopolitical struggles between 1900 and 1999 that reshaped global power structures, societies, and ideologies.
-
E.
theater of the War of the Spanish Succession
The theater of the War of the Spanish Succession is the geographic and operational arena—spanning various European regions and overseas territories—where the military campaigns, battles, and maneuvers of that war took place.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.