Triple
T28291433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African Schools Act |
E713435
|
entity |
| Predicate | gradeRangeForCompulsoryAttendance |
P111887
|
FINISHED |
| Object | Grade 1 to Grade 9 |
—
|
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: Grade 1 to Grade 9 | Statement: [South African Schools Act, gradeRangeForCompulsoryAttendance, Grade 1 to Grade 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeRangeForCompulsoryAttendance Context triple: [South African Schools Act, gradeRangeForCompulsoryAttendance, Grade 1 to Grade 9]
-
A.
gradeRange
Indicates the span of grades or scores that an item, performance, or entity falls within.
-
B.
hasEnrollmentRange
Indicates that there is a specified minimum and/or maximum number of participants allowed or expected for an enrollment in a given context.
-
C.
gradeRangeStart
Indicates the lower boundary value at which a particular grade or grading interval begins.
-
D.
maximumAttendanceRecord
Indicates that an entity holds the highest recorded attendance value within a given context or dataset.
-
E.
gradeRangeContext
chosen
Indicates the range or span of grades within which a particular condition, evaluation, or context applies.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64484910c81908f66d35cfdaa3cc4 |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:29 p.m.