Triple
T4317035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Registrar’s Office of UC Berkeley |
E96418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | registrar’s office |
C1291
|
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: registrar’s office Context triple: [Registrar’s Office of UC Berkeley, instanceOf, registrar’s office]
-
A.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
B.
court office
A court office is an administrative unit within a judicial system responsible for managing case records, scheduling hearings, processing legal documents, and supporting the day-to-day operations of the court.
-
C.
clerical office
A clerical office is a workplace where administrative tasks such as record-keeping, correspondence, data entry, and document management are performed to support an organization’s operations.
-
D.
academic administrative office
chosen
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
E.
court clerk office
A court clerk office is the administrative hub of a court system responsible for managing case records, processing legal documents, scheduling hearings, and providing procedural information to judges, attorneys, and the public.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:12 p.m.