Triple
T34510624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem City School District |
E886007
|
entity |
| Predicate | schoolBoardRole |
P84912
|
FINISHED |
| Object | sets policy for the district |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: sets policy for the district | Statement: [Salem City School District, schoolBoardRole, sets policy for the district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolBoardRole Context triple: [Salem City School District, schoolBoardRole, sets policy for the district]
-
A.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
-
B.
schoolBoardMembers
Indicates that certain individuals serve as members of a particular school board.
-
C.
schoolBoardSystem
chosen
Indicates a governance or administrative relationship in which a school board oversees, manages, or makes decisions for a school system or district.
-
D.
schoolRole
Indicates the specific function, position, or capacity an entity holds within a school context (e.g., student, teacher, administrator).
-
E.
schoolBoardElected
Indicates that a school board has been chosen or selected through an election process.
- F. None of above.
Provenance (3 batches)
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:01 a.m.