Triple
T35409269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siersma Elementary School |
E1023458
|
entity |
| Predicate | isInSchoolDistrictType |
P58636
|
FINISHED |
| Object | public school 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: public school district | Statement: [Siersma Elementary School, isInSchoolDistrictType, public school district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInSchoolDistrictType Context triple: [Siersma Elementary School, isInSchoolDistrictType, public school district]
-
A.
typeOfSchoolDistrict
chosen
Indicates the classification or category of a school district, specifying what kind of school district it is.
-
B.
hasSchoolDistricts
Indicates that one entity administers, contains, or is associated with one or more school districts.
-
C.
isOnlySchoolOfDistrict
Indicates that the school is the sole educational institution within its district.
-
D.
hasSchoolBoardType
Indicates the specific governance or organizational structure type of a school board associated with an educational institution or district.
-
E.
hasPublicSchoolDistrictCode
Indicates that an entity is associated with a specific public school district identified by a district code.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79564e2348190ba2a1badfe33b995 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.