Triple
T15009379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Officer Course |
E377793
|
entity |
| Predicate | academicYears |
P52828
|
FINISHED |
| Object | junior year of college |
—
|
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: junior year of college | Statement: [Professional Officer Course, academicYears, junior year of college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicYears Context triple: [Professional Officer Course, academicYears, junior year of college]
-
A.
academicYearType
Indicates the classification of an academic year according to its structural or administrative type (e.g., semester-based, quarter-based, fiscal year, etc.).
-
B.
lectureYears
Indicates the years during which a lecture or course is (or was) delivered.
-
C.
schoolYear
chosen
Indicates the academic year or grade level in which an entity (typically a student or class) is situated within an educational system.
-
D.
applicationYear
Indicates the year in which an application was submitted or made.
-
E.
typicalAcademicYearStart
Indicates the usual calendar date or period when an academic year customarily begins for an institution or system.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded734943481908dad4ceed4fe850c |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.