Triple
T16705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everett Public Schools |
E332
|
entity |
| Predicate | schoolType |
P110
|
FINISHED |
| Object | urban 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: urban school district | Statement: [Everett Public Schools, schoolType, urban school district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolType Context triple: [Everett Public Schools, schoolType, urban school district]
-
A.
educationType
Indicates the specific category or level of education associated with an entity, such as formal, informal, primary, secondary, or higher education.
-
B.
typeOfInstitution
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
-
C.
campusType
chosen
Indicates the classification or category of a campus based on its type (e.g., main, satellite, urban, rural).
-
D.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
-
E.
schoolDistrict
Indicates that one entity is a school district that administers, oversees, or serves the other entity (such as a school or geographic area).
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a241ea1ea081908e8a81ca97531ba5 |
completed | Feb. 28, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69a23fec1fe8819080da6f2c745dc8fd |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.