Triple
T26902971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Civil Code |
E678079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of California law |
C48953
|
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: source of California law Context triple: [California Civil Code, instanceOf, source of California law]
-
A.
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.
-
B.
source of civil law
chosen
A source of civil law is any authoritative origin—such as statutes, judicial decisions, customs, or legal doctrine—from which binding civil legal rules are derived and recognized within a legal system.
-
C.
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.
-
D.
source of constitutional law
A source of constitutional law is any authoritative origin—such as a written constitution, judicial decisions, conventions, or scholarly writings—from which the fundamental rules and principles governing a state’s constitutional order are derived.
-
E.
United States state law
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:51 a.m.