Triple
T37143417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbott v. Burke line of cases |
E920176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school finance litigation |
C5892
|
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: school finance litigation Context triple: [Abbott v. Burke line of cases, instanceOf, school finance litigation]
-
A.
school finance system
A school finance system is a software solution that manages budgeting, accounting, payroll, purchasing, and financial reporting for educational institutions to ensure accurate, compliant, and transparent use of funds.
-
B.
education law
chosen
Education law is the body of statutes, regulations, and case law that governs how educational institutions operate, the rights and responsibilities of students, parents, teachers, and administrators, and the allocation and oversight of educational resources.
-
C.
compulsory education case
A compulsory education case is a legal or administrative proceeding that addresses whether a child, parent, or school has complied with laws requiring school attendance and basic educational provision.
-
D.
school segregation case
A school segregation case is a legal dispute challenging the separation of students into different schools or classrooms based on race or related factors, typically alleging violations of equal protection or civil rights laws.
-
E.
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.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.