Triple
T20618411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Carolina Technical College System |
E506628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statewide technical college system |
C5884
|
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: statewide technical college system Context triple: [South Carolina Technical College System, instanceOf, statewide technical college system]
-
A.
community college system
chosen
A community college system is a coordinated network of publicly funded two-year colleges that collectively provide accessible, affordable postsecondary education, vocational training, and transfer pathways within a defined region or state.
-
B.
state system
A state system is a structured framework in which distinct political entities (states) interact under shared norms, rules, and institutions that regulate their behavior and relationships.
-
C.
technical college campus
A technical college campus is a specialized educational environment comprising classrooms, labs, workshops, and support facilities designed to provide hands-on, career-focused training in applied sciences, trades, and technologies.
-
D.
state university system
A state university system is a coordinated network of public higher education institutions within a state, governed by a central authority to manage funding, policy, and academic standards.
-
E.
community college district
A community college district is a geographically defined administrative entity that oversees and coordinates the operation, governance, and funding of one or more community colleges 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.