Triple
T30652147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okemos High School |
E780288
|
entity |
| Predicate | schoolDistrictHeadquartersLocation |
P94457
|
FINISHED |
| Object | Okemos, Michigan |
—
|
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: Okemos, Michigan | Statement: [Okemos High School, schoolDistrictHeadquartersLocation, Okemos, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolDistrictHeadquartersLocation Context triple: [Okemos High School, schoolDistrictHeadquartersLocation, Okemos, Michigan]
-
A.
schoolDistrictHeadquartersLocatedIn
chosen
Indicates that the administrative headquarters of a school district is located within a specified geographic place.
-
B.
schoolDistrict
Indicates that one entity is a school district that administers, oversees, or serves the other entity (such as a school or geographic area).
-
C.
schoolBoardDistricts
Indicates the specific school board district that has jurisdiction over or is associated with an entity.
-
D.
schoolLocation
Indicates the place or area where a school is situated or operates.
-
E.
districtHeadquartersLocation
Indicates the place where the administrative headquarters of a district is located.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:30 p.m.