Triple
T18619520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 Accord |
E455111
|
entity |
| Predicate | mentionsTemperatureLimit |
P107019
|
FINISHED |
| Object | 2 °C above pre-industrial levels |
—
|
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 °C above pre-industrial levels | Statement: [COP15 Accord, mentionsTemperatureLimit, 2 °C above pre-industrial levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsTemperatureLimit Context triple: [COP15 Accord, mentionsTemperatureLimit, 2 °C above pre-industrial levels]
-
A.
hasTemperatureCriterion
chosen
Indicates that something is associated with a specific temperature-based condition or requirement that must be met.
-
B.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
maximumForGivenTemperatures
Indicates the maximum value attained when considering a specified set or range of temperatures.
-
D.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
E.
temperatureRangeVariant
Indicates a relationship where one temperature range is a variation or alternative form of another temperature range.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.