Triple
T21857777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medinah Intermediate School |
E539675
|
entity |
| Predicate | hasGradeLevelRange |
P93763
|
FINISHED |
| Object | intermediate elementary grades |
—
|
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: intermediate elementary grades | Statement: [Medinah Intermediate School, hasGradeLevelRange, intermediate elementary grades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradeLevelRange Context triple: [Medinah Intermediate School, hasGradeLevelRange, intermediate elementary grades]
-
A.
hasGradeSpan
chosen
Indicates the range of grade levels or educational stages that an entity (such as a school or program) covers or serves.
-
B.
eligibleGradeLevels
Indicates the grade levels for which something (such as a program, course, or benefit) is considered eligible or applicable.
-
C.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
-
D.
gradeRange
Indicates the span of grades or scores that an item, performance, or entity falls within.
-
E.
gradeRangeStart
Indicates the lower boundary value at which a particular grade or grading interval begins.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d638721c8190918fc6ad9c5d5bf6 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.