Triple
T1412227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agenda 2063 |
E31829
|
entity |
| Predicate | hasGoalYear |
P26643
|
FINISHED |
| Object | 2063 |
—
|
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: 2063 | Statement: [Agenda 2063, hasGoalYear, 2063]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoalYear Context triple: [Agenda 2063, hasGoalYear, 2063]
-
A.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
B.
hasManagementGoal
Indicates that an entity is associated with a specific management objective or target it is intended to achieve or support.
-
C.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
hasNumberInYear
Indicates that a specific number is associated with or occurs within a given year.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e3383c81909acb9c6c1c3b817a |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:59 p.m.