Triple
T26571711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Public Schools |
E666843
|
entity |
| Predicate | primarySchoolDistrictFor |
P226
|
FINISHED |
| Object | Seattle |
—
|
NE NERFINISHED |
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: Seattle | Statement: [Seattle Public Schools, primarySchoolDistrictFor, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySchoolDistrictFor Context triple: [Seattle Public Schools, primarySchoolDistrictFor, Seattle]
-
A.
schoolDistrict
chosen
Indicates that one entity is a school district that administers, oversees, or serves the other entity (such as a school or geographic area).
-
B.
previousSchoolDistrict
Indicates the school district in which an entity (typically a student) was enrolled or associated before their current school district.
-
C.
schoolDistrictHeadquartersLocatedIn
Indicates that the administrative headquarters of a school district is located within a specified geographic place.
-
D.
sharesRegionalSchoolDistrictWith
Indicates that two entities are part of, or served by, the same regional school district.
-
E.
schoolBoardDistricts
Indicates the specific school board district that has jurisdiction over or is associated with an entity.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 27, 2026, 1:58 a.m.