Triple
T22678017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Trustees of Brooklyn Public Library |
E560398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | library governing body |
C172
|
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: library governing body Context triple: [Board of Trustees of Brooklyn Public Library, instanceOf, library governing body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
C.
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.
-
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.
library committee
A library committee is a group of individuals responsible for guiding the development, management, and policies of a library’s collections, services, and resources.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:11 p.m.