Triple
T25464466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Carbon Fuel Standard |
E638136
|
entity |
| Predicate | policyDesign |
P4331
|
FINISHED |
| Object | technology-neutral standard |
—
|
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: technology-neutral standard | Statement: [Low Carbon Fuel Standard, policyDesign, technology-neutral standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyDesign Context triple: [Low Carbon Fuel Standard, policyDesign, technology-neutral standard]
-
A.
policyDesignation
Indicates that an entity is assigned or labeled with a specific policy or policy classification.
-
B.
policyAim
Indicates that a policy is intended to achieve, promote, or be directed toward a particular goal or objective.
-
C.
policyConcept
Indicates that one entity is a policy and the other is a conceptual element or idea that defines, characterizes, or underlies that policy.
-
D.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
E.
policyApproach
chosen
Indicates the strategy, method, or overall course of action adopted in creating, implementing, or managing a policy.
- F. None of above.
Provenance (3 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 2:13 p.m.