Triple
T8956109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCP2.6 |
E213474
|
entity |
| Predicate | radiativeForcingLevel |
P85859
|
FINISHED |
| Object | 2.6 W/m² by 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: 2.6 W/m² by 2100 | Statement: [RCP2.6, radiativeForcingLevel, 2.6 W/m² by 2100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiativeForcingLevel Context triple: [RCP2.6, radiativeForcingLevel, 2.6 W/m² by 2100]
-
A.
climateSensitivity
Indicates how strongly a system’s temperature responds to a change in external forcing, such as increased greenhouse gas concentrations.
-
B.
representationLevel
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
-
C.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
-
D.
radiantIn
Indicates that one entity emits or shines light, energy, or brilliance within or into another entity or space.
-
E.
affectedLevel
Indicates the degree or extent to which one entity is impacted or influenced by another entity or event.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6728965881908e9f14aaee0c5a18 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.