Triple

T30189519
Position Surface form Disambiguated ID Type / Status
Subject RCP3-PD E767433 entity
Predicate hasRadiativeForcingLevel P85859 FINISHED
Object approximately 3 W/m² in 2100 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: approximately 3 W/m² in 2100 | Statement: [RCP3-PD, hasRadiativeForcingLevel, approximately 3 W/m² in 2100]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRadiativeForcingLevel
Context triple: [RCP3-PD, hasRadiativeForcingLevel, approximately 3 W/m² in 2100]
  • A. radiativeForcingLevel chosen
    Indicates the magnitude of change in the Earth’s energy balance caused by a given factor (e.g., greenhouse gases or aerosols), typically expressed as a level of radiative forcing.
  • B. inForceLevel
    Indicates that an entity exists or operates within a specified level, tier, or intensity of force, power, or influence.
  • C. climateSensitivity
    Indicates how strongly a system’s temperature responds to a change in external forcing, such as increased greenhouse gas concentrations.
  • D. hasRadiatedEnergy
    Indicates that an entity has emitted or released energy in the form of radiation.
  • E. radiationLevel
    Indicates the intensity or amount of radiation present in or emitted by an entity or environment.
  • 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_69f2247cc3d88190811dec3face94bf5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7675b12848190a3569cfda29c5b0e completed May 3, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69f762f4b59481909f70074f11825bfb completed May 3, 2026, 3 p.m.
Created at: April 29, 2026, 7:28 p.m.