Triple
T24415286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teacher Regulation Branch of British Columbia |
E615567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | teacher regulatory authority |
C1181
|
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: teacher regulatory authority Context triple: [Teacher Regulation Branch of British Columbia, instanceOf, teacher regulatory authority]
-
A.
education regulatory authority
An education regulatory authority is a governing body responsible for setting, monitoring, and enforcing standards, policies, and regulations to ensure the quality, equity, and compliance of educational institutions and systems.
-
B.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
C.
school district official
A school district official is an administrative leader responsible for overseeing and coordinating the policies, operations, and educational standards across multiple schools within a district.
-
D.
academic regulation
Academic regulation is a formal set of rules and policies established by educational institutions or governing bodies to guide, control, and standardize academic activities, standards, and behaviors.
-
E.
teacher training institute
A teacher training institute is an educational organization dedicated to preparing, developing, and certifying individuals for effective professional teaching through theoretical instruction and practical classroom experience.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:12 a.m.