Triple
T4524504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 350.org |
E103344
|
entity |
| Predicate | defines350ppmAs |
P773
|
FINISHED |
| Object | safe upper limit of CO2 in the atmosphere |
—
|
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: safe upper limit of CO2 in the atmosphere | Statement: [350.org, defines350ppmAs, safe upper limit of CO2 in the atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defines350ppmAs Context triple: [350.org, defines350ppmAs, safe upper limit of CO2 in the atmosphere]
-
A.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
B.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
C.
divisionDefinedBy
Indicates that a division or partition is established or characterized according to a specified rule, criterion, or defining entity.
-
D.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
E.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5773341c8190bf27745feb863575 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.