Triple
T30676128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California renewable portfolio standard |
E780912
|
entity |
| Predicate | coveredResource |
P180891
|
FINISHED |
| Object | solar energy |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: solar energy | Statement: [California renewable portfolio standard, coveredResource, solar energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredResource Context triple: [California renewable portfolio standard, coveredResource, solar energy]
-
A.
discoveredResource
Indicates that an entity has found, identified, or uncovered a particular resource.
-
B.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
C.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
-
D.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
E.
resourceExtracted
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
- F. None of above. chosen
Provenance (4 batches)
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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 29, 2026, 8:32 p.m.