Triple
T10758464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A True Relation of Such Occurrences and Accidents of Note as Hath Happened in Virginia |
E253761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial report |
C28512
|
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: colonial report Context triple: [A True Relation of Such Occurrences and Accidents of Note as Hath Happened in Virginia, instanceOf, colonial report]
-
A.
colonial commission report
A colonial commission report is an official document produced by a specially appointed body in a colonial context, detailing investigations, findings, and recommendations on specific issues affecting the colony.
-
B.
colonial committee
A colonial committee is a governing or advisory body established within a colony to oversee local administration, implement policies from the colonial power, and address political, economic, or social issues affecting the colonial territory.
-
C.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
D.
colonial policy
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
-
E.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:15 p.m.