Triple
T7111358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollution Prevention Act of 1990 |
E165713
|
entity |
| Predicate | policyHierarchy |
P61392
|
FINISHED |
| Object | source reduction |
—
|
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: source reduction | Statement: [Pollution Prevention Act of 1990, policyHierarchy, source reduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyHierarchy Context triple: [Pollution Prevention Act of 1990, policyHierarchy, source reduction]
-
A.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
B.
policyDomain
Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
-
C.
policyElement
chosen
Indicates that something is a component or constituent part of a broader policy.
-
D.
powerStructure
Indicates how authority, control, and decision-making are distributed and organized among entities within a system or group.
-
E.
policyCategory
Indicates the classification or type of policy under which an item, rule, or action is grouped.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.