Triple
T24412083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Course At A Time block plan |
E615479
|
entity |
| Predicate | typicalCourseLoad |
P49837
|
FINISHED |
| Object | one course per term |
—
|
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: one course per term | Statement: [One Course At A Time block plan, typicalCourseLoad, one course per term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCourseLoad Context triple: [One Course At A Time block plan, typicalCourseLoad, one course per term]
-
A.
typicalCourse
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
-
B.
typicalEnrollment
Indicates the usual or standard number of participants or members enrolled in something, such as a course, program, or institution.
-
C.
numberOfCourses
chosen
Indicates the quantity of courses associated with a given entity.
-
D.
hasTypicalCourse
Indicates that there is a characteristic or commonly observed progression, sequence, or development pattern associated with the subject.
-
E.
typicalClassSize
Indicates the usual or average number of students (or participants) that are present in a single class or course section.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958241e48190ae33297c5c5c0e59 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:10 a.m.