Triple

T1460745
Position Surface form Disambiguated ID Type / Status
Subject Acid Rain Program E31505 entity
Predicate regulatesEmissionOf P17326 FINISHED
Object sulfur dioxide 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: sulfur dioxide | Statement: [Acid Rain Program, regulatesEmissionOf, sulfur dioxide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatesEmissionOf
Context triple: [Acid Rain Program, regulatesEmissionOf, sulfur dioxide]
  • A. emissionsControl chosen
    Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
  • B. environmentalRegulation
    Indicates that one entity imposes rules, standards, or restrictions on another entity’s activities to protect or manage the natural environment.
  • C. annexVIRegulates
    Indicates that a subject is governed or controlled by the rules and provisions set out in Annex VI.
  • D. hasEnvironmentalRegulationCompliance
    Indicates that an entity adheres to or fulfills applicable environmental regulations, standards, or compliance requirements.
  • E. emitted
    Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
  • 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_69a49917dfc081909acdbdf5d684f1ef completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c59d6dd88190b8ff3bda90aef7e2 completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47ec5108190b1772237f2e5d90b completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.