Triple
T35894932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 17 of the California Code of Regulations |
E1038193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Title 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: Title of the California Code of Regulations Context triple: [Title 17 of the California Code of Regulations, instanceOf, Title 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.
title of the Code of Federal Regulations
The title of the Code of Federal Regulations is the top-level organizational division that groups together all federal regulations pertaining to a broad subject area, such as labor, environment, or transportation.
-
C.
Title of Colorado Revised Statutes
The "Title of Colorado Revised Statutes" is the top-level organizational label that identifies and categorizes a broad subject area within the codified laws of the State of Colorado.
-
D.
Title of the Colorado Revised Statutes
The Title of the Colorado Revised Statutes is a primary organizational division that groups together all statutes related to a broad subject area within Colorado state law.
-
E.
statutory code title
A statutory code title is a major organizational division within a jurisdiction’s codified laws that groups together statutes related to a broad subject area under a unified heading and numbering scheme.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.