Triple
T28653316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Liberian general election |
E725258
|
entity |
| Predicate | peaceAgreementFramework |
P138988
|
FINISHED |
| Object | Abuja peace accords |
—
|
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: Abuja peace accords | Statement: [1997 Liberian general election, peaceAgreementFramework, Abuja peace accords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peaceAgreementFramework Context triple: [1997 Liberian general election, peaceAgreementFramework, Abuja peace accords]
-
A.
peaceTerms
Indicates the conditions or agreements proposed or accepted by parties to establish or maintain peace after or during a conflict.
-
B.
hasPeaceAccord
chosen
Indicates that a formal peace agreement or treaty exists between the related entities, establishing terms to end or prevent conflict.
-
C.
ceasefireAgreements
Indicates that parties involved in a conflict have formally agreed to suspend hostilities, typically under specified terms and conditions.
-
D.
peaceProcessInvolved
Indicates that an entity participates in, contributes to, or is otherwise involved in a formal peace process or peace negotiations.
-
E.
peaceAccordDate
Indicates the date on which a formal peace accord between parties was signed or came into effect.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:53 a.m.