Triple
T34281351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Smith Northside High School Grizzlies |
E879597
|
entity |
| Predicate | representsGrades |
P111934
|
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: [Fort Smith Northside High School Grizzlies, representsGrades, 9–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsGrades Context triple: [Fort Smith Northside High School Grizzlies, representsGrades, 9–12]
-
A.
includesGrades
chosen
Indicates that one entity contains or encompasses the grade information associated with another entity.
-
B.
denotesGrade
Indicates that an entity assigns, specifies, or is associated with a particular grade or evaluation for another entity.
-
C.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
D.
servesStudentsToGrade
Indicates that an entity provides educational services or instruction to students up to a specified grade level.
-
E.
isGraded
Indicates that an entity has been evaluated and assigned a grade or score, typically by an assessor or grading process.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:57 a.m.