Triple
T23327728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Lyon County USD 251 |
E591342
|
entity |
| Predicate | hasSchoolDistrictNumber |
P54119
|
FINISHED |
| Object | 251 |
—
|
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: 251 | Statement: [North Lyon County USD 251, hasSchoolDistrictNumber, 251]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolDistrictNumber Context triple: [North Lyon County USD 251, hasSchoolDistrictNumber, 251]
-
A.
hasSchoolDistricts
Indicates that one entity administers, contains, or is associated with one or more school districts.
-
B.
schoolDistrictNumber
chosen
Indicates the specific numerical identifier assigned to the school district with which an entity is associated.
-
C.
hasHighSchoolSendingDistrict
Indicates that one school district serves as the designated high school destination for students coming from another (typically non-high-school) sending district.
-
D.
sharesRegionalSchoolDistrictWith
Indicates that two entities are part of, or served by, the same regional school district.
-
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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197eb6cd481908acd5619b3af246d |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:13 p.m.