Triple
T7717461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayonne School District |
E174920
|
entity |
| Predicate | hasHighSchoolGrades |
P78216
|
FINISHED |
| Object | 9–12 |
—
|
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: 9–12 | Statement: [Bayonne School District, hasHighSchoolGrades, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighSchoolGrades Context triple: [Bayonne School District, hasHighSchoolGrades, 9–12]
-
A.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
B.
highSchoolAchievement
Indicates the level or nature of a person’s academic or related performance outcomes during their high school education.
-
C.
hasSchool
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
D.
hasNotableHighSchool
Indicates that an entity is associated with a high school that is particularly notable or significant in some recognized way.
-
E.
hasUpperSchool
chosen
Indicates that an educational institution includes or is associated with an upper-level school (typically serving older or advanced students).
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.