Triple
T2035179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Kunshan University |
E44608
|
entity |
| Predicate | hasAcademicCalendarType |
P780
|
FINISHED |
| Object | semester system |
—
|
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: semester system | Statement: [Duke Kunshan University, hasAcademicCalendarType, semester system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcademicCalendarType Context triple: [Duke Kunshan University, hasAcademicCalendarType, semester system]
-
A.
academicCalendar
chosen
Indicates the schedule or structure of academic terms, sessions, and key dates associated with an educational institution or program.
-
B.
hasFacultyType
Indicates that a faculty member or academic unit is associated with a specific category or type of faculty (e.g., full-time, adjunct, visiting).
-
C.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
D.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
E.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb934ff948190acd88d4f587463a4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.