Triple
T30395681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawda Jawara |
E773211
|
entity |
| Predicate | coupLeaderOpposedBy |
P169156
|
FINISHED |
| Object | Yahya Jammeh |
—
|
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: Yahya Jammeh | Statement: [Dawda Jawara, coupLeaderOpposedBy, Yahya Jammeh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coupLeaderOpposedBy Context triple: [Dawda Jawara, coupLeaderOpposedBy, Yahya Jammeh]
-
A.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
B.
coupParticipantIn
Indicates that an entity took part in, contributed to, or was involved in carrying out a specific coup event.
-
C.
opposedLeader
Indicates that one entity actively resisted, challenged, or worked against the leadership or authority of another entity.
-
D.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
E.
coupAttemptedAgainst
Indicates that an effort was made to overthrow or forcibly remove the target entity from power, typically through illegal or unconstitutional means.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685ac63248190a51b9e0e6ed89dab |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:02 p.m.