Triple
T37576746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakland County public school system |
E934842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of school districts |
C12411
|
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: network of school districts Context triple: [Oakland County public school system, instanceOf, network of school districts]
-
A.
school network
chosen
A school network is a connected system of schools, resources, and stakeholders that collaborates to share information, coordinate activities, and support educational goals across multiple institutions.
-
B.
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.
-
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.
statewide school system
A statewide school system is a coordinated network of public educational institutions, policies, and administrative bodies that operate under a unified state authority to provide standardized education across all regions within the state.
-
E.
multi-campus educational network
A multi-campus educational network is an interconnected system of geographically distributed campuses that share academic programs, resources, governance, and support services to deliver coordinated, high-quality education across multiple locations.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.