Triple
T8750520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduate School regulations of the University of Tokyo |
E207946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal rule |
C21055
|
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: internal rule Context triple: [Graduate School regulations of the University of Tokyo, instanceOf, internal rule]
-
A.
internal regulation
Internal regulation is the set of processes and mechanisms by which a system monitors and adjusts its own internal states and activities to maintain stability and achieve its goals.
-
B.
internal statute
chosen
An internal statute is a formal, binding rule or regulation adopted within an organization to govern its internal operations, decision-making processes, and member conduct.
-
C.
subrule
A subrule is a subordinate rule that refines, constrains, or specifies the conditions and behavior of a broader parent rule within a rule-based system.
-
D.
policy rule
A policy rule is a formal, enforceable statement that defines specific conditions and corresponding actions or constraints to guide decision-making and behavior within a system or organization.
-
E.
formal rules
Formal rules are explicitly defined, codified guidelines or principles that govern behavior, procedures, or decision-making within a specific system or organization.
- F. None of above.
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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:39 p.m.