Triple
T2348016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacon's Rebellion |
E45177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in colonial Virginia |
C383
|
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: event in colonial Virginia Context triple: [Bacon's Rebellion, instanceOf, event in colonial Virginia]
-
A.
colonial-era event
chosen
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
B.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred during the 1675–1678 conflict between Native American tribes and English colonists in New England.
-
C.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred between 1675 and 1678 during the conflict between Native American tribes and English colonists in New England.
-
D.
English colonial settlement
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
-
E.
county in Virginia
A county in Virginia is a primary local government and geographic subdivision of the Commonwealth of Virginia, responsible for providing regional services, administration, and governance to the communities within its boundaries.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:52 p.m.