Triple
T4582462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen Accord |
E101885
|
entity |
| Predicate | recognizedTemperatureGoal |
P58118
|
FINISHED |
| Object | 2 degrees Celsius limit |
—
|
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 degrees Celsius limit | Statement: [Copenhagen Accord, recognizedTemperatureGoal, 2 degrees Celsius limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedTemperatureGoal Context triple: [Copenhagen Accord, recognizedTemperatureGoal, 2 degrees Celsius limit]
-
A.
settingClimate
Indicates that an entity adjusts or defines the climate or environmental conditions for another entity or context.
-
B.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
temperatureControlMethod
Indicates the method or mechanism used to regulate or maintain a desired temperature.
-
D.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
-
E.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59029568819091db1e77a9a2ec41 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.