Triple
T27995790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray City School District offices |
E707008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school district administrative office |
C50609
|
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 district administrative office Context triple: [Murray City School District offices, instanceOf, school district administrative office]
-
A.
school district headquarters
chosen
The school district headquarters is the central administrative facility where district-wide educational policies are set, resources are managed, and support services are coordinated for all schools in the district.
-
B.
school district official
A school district official is an administrative leader responsible for overseeing and coordinating the policies, operations, and educational standards across multiple schools within a 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.
public administration school
A public administration school is an educational institution that prepares students for careers in government and public service by teaching policy analysis, management, and leadership in the public sector.
-
E.
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.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:53 p.m.