Triple
T30942697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camden District, South Carolina |
E788303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era administrative district |
C37564
|
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-era administrative district Context triple: [Camden District, South Carolina, instanceOf, colonial-era administrative district]
-
A.
colonial district
chosen
A colonial district is an administrative subdivision established by a colonial power to govern, control, and organize a specific geographic area within its overseas territories.
-
B.
colonial-era organization
A colonial-era organization is a formal group or institution established during a period of colonial rule to administer, exploit, or manage political, economic, social, or cultural affairs in a colonized territory.
-
C.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
D.
administrative division of the Colony of Virginia
An administrative division of the Colony of Virginia was a geographically defined governmental unit, such as a county or parish, established by colonial authorities to organize local governance, law enforcement, taxation, and land administration.
-
E.
ancient district
An ancient district is a historically defined administrative or geographic area that existed in antiquity, often characterized by distinct political, cultural, or social functions within a larger civilization.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:53 p.m.