Triple
T26612981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avella Area School District |
E667975
|
entity |
| Predicate | governsGradesFrom |
P54120
|
FINISHED |
| Object | kindergarten |
—
|
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: kindergarten | Statement: [Avella Area School District, governsGradesFrom, kindergarten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsGradesFrom Context triple: [Avella Area School District, governsGradesFrom, kindergarten]
-
A.
overseesGrades
Indicates that one entity is responsible for monitoring, managing, or supervising the academic grades of another entity.
-
B.
includesGrades
Indicates that one entity contains or encompasses the grade information associated with another entity.
-
C.
regulatesGradeLevels
chosen
Indicates a relationship where one entity sets or enforces rules or standards governing the grade levels of another entity.
-
D.
isGradeWithin
Indicates that a given grade value falls within a specified acceptable or defined grade range.
-
E.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:17 a.m.