Triple
T24665206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte-Mecklenburg Board of Education |
E610655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local education agency governing body |
C8900
|
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: local education agency governing body Context triple: [Charlotte-Mecklenburg Board of Education, instanceOf, local education agency governing body]
-
A.
school district governing body
chosen
A school district governing body is an elected or appointed group responsible for setting policies, overseeing budgets, and guiding the overall direction and accountability of the public schools within a specific district.
-
B.
school governing body
A school governing body is a group of elected and appointed individuals responsible for setting the strategic direction, policies, and oversight of a school’s management and performance.
-
C.
school board
A school board is a governing body of elected or appointed members responsible for setting policies, overseeing budgets, and guiding the strategic direction of a school district.
-
D.
school district
A school district is an administrative unit that manages and oversees a group of public schools within a defined geographic area, including their policies, funding, staffing, and educational programs.
-
E.
state education agency
A state education agency is a government body responsible for overseeing, regulating, and supporting public education within a U.S. state, including setting academic standards, administering funding, and ensuring compliance with education laws.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:36 a.m.