Triple
T29628216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undergraduate School regulations of the University of Tokyo |
E755201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student conduct code |
C55982
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: student conduct code Context triple: [Undergraduate School regulations of the University of Tokyo, instanceOf, student conduct code]
-
A.
student conduct office
The student conduct office is a university department responsible for investigating alleged student misconduct, enforcing institutional policies, and promoting a safe, respectful campus community through education and accountability processes.
-
B.
student conduct organization
A student conduct organization is a campus body responsible for upholding institutional policies by investigating alleged student misconduct, facilitating fair hearings, and implementing educational or disciplinary outcomes.
-
C.
student affairs committee
A student affairs committee is a group responsible for overseeing, supporting, and improving students’ non-academic experiences, services, and well-being within an educational institution.
-
D.
student section
A student section is a group of students enrolled together in the same course offering, typically sharing the same schedule, instructor, and classroom or online space.
-
E.
university statute book
A university statute book is an official compilation of the institution’s fundamental rules, regulations, and governance provisions that define its structure, authorities, and procedures.
- F. None of above. chosen
Provenance (1 batch)
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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:39 p.m.