Triple
T29382995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Africa-EU Strategy |
E745181
|
entity |
| Predicate | thirdActionPlanPeriod |
P144419
|
FINISHED |
| Object | 2014–2017 |
—
|
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: 2014–2017 | Statement: [Joint Africa-EU Strategy, thirdActionPlanPeriod, 2014–2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdActionPlanPeriod Context triple: [Joint Africa-EU Strategy, thirdActionPlanPeriod, 2014–2017]
-
A.
lastPlan
Indicates that one plan is the final or most recent plan in a sequence of plans associated with an entity or process.
-
B.
thirdCycle
chosen
Indicates that the related entity is in, associated with, or pertains to the third cycle or third iteration within a defined sequence, process, or phase.
-
C.
secondPlanStartYear
Indicates the calendar year in which a second or subsequent plan begins.
-
D.
secondCyclePeriod
Indicates the duration or interval of time associated with a second occurrence or cycle of a recurring process or event.
-
E.
thirdQuarter
Indicates that something occurs in, belongs to, or is associated with the third quarter of a defined time period (such as a fiscal or calendar year).
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 2:36 p.m.