Triple
T29723704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISWAP |
E752122
|
entity |
| Predicate | listedAsTerroristOrganizationBy |
P21106
|
FINISHED |
| Object | Nigeria |
E2050
|
NE 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: Nigeria | Statement: [ISWAP, listedAsTerroristOrganizationBy, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedAsTerroristOrganizationBy Context triple: [ISWAP, listedAsTerroristOrganizationBy, Nigeria]
-
A.
classifiedAsTerroristBy
chosen
Indicates that an entity has been designated or labeled as a terrorist by a specified authority, organization, or actor.
-
B.
hasTerroristOrganization
Indicates that an entity is associated with, belongs to, or functions as a terrorist organization.
-
C.
terroristOrganization
Indicates that an entity is recognized as a group that plans, supports, or carries out acts of terrorism.
-
D.
declaredCriminalOrganizationIn
Indicates that an authority has officially designated a group as a criminal organization within a specific jurisdiction or location.
-
E.
positionOnTerrorism
Indicates a stance or viewpoint that an entity holds regarding terrorism, such as its causes, legitimacy, or appropriate responses.
- F. None of above.
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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fe1b2881909acfdfed7c4a1ac2 |
completed | May 2, 2026, 9:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8e2c37c8190b9f9a0df727ccefb |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:38 p.m.