Triple
T35969531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 2.5 of the California Code of Regulations |
E1040241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | part of the California Code of Regulations |
C12054
|
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: part of the California Code of Regulations Context triple: [Title 2.5 of the California Code of Regulations, instanceOf, part of the California Code of Regulations]
-
A.
title of the California Code of Regulations
chosen
The title of the California Code of Regulations is the official, numbered major division that organizes and identifies a broad subject area within the state's administrative regulations.
-
B.
segment of the California Rules of Court
A segment of the California Rules of Court is a distinct, formally numbered provision or subsection that prescribes specific procedural or administrative requirements governing court practice within California’s judicial system.
-
C.
California regulation
A California regulation is a legally binding rule or standard adopted by a California state agency under authority granted by statute, governing specific activities, industries, or conduct within the state.
-
D.
Code of Federal Regulations part
A Code of Federal Regulations part is a distinct subdivision within a CFR title that organizes and codifies a specific set of related federal rules and regulatory requirements.
-
E.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.