Triple
T25378068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North African Regional Capability |
E633105
|
entity |
| Predicate | isPlannedWithin |
P117581
|
FINISHED |
| Object | African Standby Force policy framework |
—
|
NE NERFINISHED |
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: African Standby Force policy framework | Statement: [North African Regional Capability, isPlannedWithin, African Standby Force policy framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedWithin Context triple: [North African Regional Capability, isPlannedWithin, African Standby Force policy framework]
-
A.
plannedIn
chosen
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
D.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e5d7e2c8190937af482e50e6cad |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:38 p.m.