Triple
T25660066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roseville Area Schools (Independent School District 623) |
E643351
|
entity |
| Predicate | hasSchoolNumber |
P163026
|
FINISHED |
| Object | 623 |
—
|
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: 623 | Statement: [Roseville Area Schools (Independent School District 623), hasSchoolNumber, 623]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolNumber Context triple: [Roseville Area Schools (Independent School District 623), hasSchoolNumber, 623]
-
A.
hasSchool
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
B.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
-
C.
hasSchoolsAccess
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
D.
hasSchoolYears
Indicates a relationship where an educational institution is associated with specific academic years or grade levels it offers or covers.
-
E.
hasSchoolOrganization
Indicates that an educational institution is associated with or contains a specific school-related organization or group.
- F. None of above. chosen
Provenance (4 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 21, 2026, 6:51 p.m.