Triple
T35873378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New South Wales education system |
E1037287
|
entity |
| Predicate | schoolYearCalendar |
P780
|
FINISHED |
| Object | four-term year |
—
|
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: four-term year | Statement: [New South Wales education system, schoolYearCalendar, four-term year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolYearCalendar Context triple: [New South Wales education system, schoolYearCalendar, four-term year]
-
A.
schoolYear
Indicates the academic year or grade level in which an entity (typically a student or class) is situated within an educational system.
-
B.
schoolYearStart
Indicates the point in time or date when a particular school year begins.
-
C.
academicCalendar
chosen
Indicates the schedule or structure of academic terms, sessions, and key dates associated with an educational institution or program.
-
D.
hasSchoolYearStructure
Indicates that an educational institution follows or is organized according to a particular school year structure or calendar pattern.
-
E.
operatesInSchoolYearSystem
Indicates that an entity functions according to, or is organized around, a specific school year calendar 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.