Triple
T25464520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Climate Scoping Plan |
E638138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | California state policy document |
C32813
|
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: California state policy document Context triple: [California Climate Scoping Plan, instanceOf, California state policy document]
-
A.
California state government publication
chosen
A California state government publication is an official document or resource produced, sponsored, or distributed by agencies or entities of the State of California to communicate information, policies, data, or services to the public or specific audiences.
-
B.
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.
-
C.
California state program
A California state program is a government-administered initiative designed to provide services, benefits, or regulatory oversight to residents, businesses, or communities within the state of California.
-
D.
California state board
A California state board is an official governing or advisory body established by state law to oversee, regulate, or provide guidance on specific public policy areas, professions, or services within California.
-
E.
state policy
A state policy is a formal set of principles and rules adopted by a government to guide decisions and actions in specific public domains such as health, education, economy, or security.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:14 p.m.