Triple
T29382993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Africa-EU Strategy |
E745181
|
entity |
| Predicate | firstActionPlanPeriod |
P190367
|
FINISHED |
| Object | 2008–2010 |
—
|
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: 2008–2010 | Statement: [Joint Africa-EU Strategy, firstActionPlanPeriod, 2008–2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstActionPlanPeriod Context triple: [Joint Africa-EU Strategy, firstActionPlanPeriod, 2008–2010]
-
A.
secondActionPlanPeriod
Indicates that something occurs or is designated within the second defined period of an action plan.
-
B.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
C.
initialAction
Indicates the first or starting action taken in a sequence of actions or events.
-
D.
hasPlanningPeriod
chosen
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
E.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
- 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_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 28, 2026, 2:36 p.m.