Triple
T33491300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Education of North Brunswick Township Public Schools |
E857745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public school district board of education |
C8555
|
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: public school district board of education Context triple: [Board of Education of North Brunswick Township Public Schools, instanceOf, public school district board of education]
-
A.
public school district
A public school district is a government-funded administrative entity responsible for managing and operating a group of public schools within a defined geographic area.
-
B.
school board
chosen
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.
-
C.
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.
-
D.
school district governing body
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.
-
E.
school board system
A school board system is an organized framework of policies, processes, and tools that supports a governing body in overseeing, managing, and making decisions about a school district’s operations, resources, and educational outcomes.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.