Triple
T18619536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 Accord |
E455111
|
entity |
| Predicate | longTermFinanceGoalYear |
P26643
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [COP15 Accord, longTermFinanceGoalYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longTermFinanceGoalYear Context triple: [COP15 Accord, longTermFinanceGoalYear, 2020]
-
A.
hasGoalYear
chosen
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
B.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
C.
planningStartYear
Indicates the calendar year in which planning for an activity, project, or process begins.
-
D.
economicGoal
Indicates that an entity has a targeted economic outcome or objective it aims to achieve.
-
E.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
- 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.