Triple
T30914110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Net Zero by 2050 roadmap |
E787531
|
entity |
| Predicate | requiresGlobalNetZeroCO2By |
P196701
|
FINISHED |
| Object | 2050 |
—
|
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: 2050 | Statement: [Net Zero by 2050 roadmap, requiresGlobalNetZeroCO2By, 2050]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresGlobalNetZeroCO2By Context triple: [Net Zero by 2050 roadmap, requiresGlobalNetZeroCO2By, 2050]
-
A.
usedCarbonOffsetting
Indicates that an entity has employed carbon offsetting measures to compensate for its greenhouse gas emissions.
-
B.
containsGreenhouseGas
Indicates that one entity includes or is composed of greenhouse gases within it.
-
C.
requiresSelfSufficiency
Indicates that an entity must be able to operate or sustain itself independently, without relying on external support or resources.
-
D.
hasCarbonFootprintCategory
Indicates that an entity is associated with a specific classification of its carbon footprint level or impact.
-
E.
CDP
Indicates a relationship where an entity is associated with or participates in a specific CDP (such as a program, platform, or process) in a defined role or capacity.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: April 29, 2026, 8:51 p.m.