Triple
T36400709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abyei |
E896615
|
entity |
| Predicate | mentionedInAgreement |
P68025
|
FINISHED |
| Object | Comprehensive Peace Agreement |
—
|
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: Comprehensive Peace Agreement | Statement: [Abyei, mentionedInAgreement, Comprehensive Peace Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInAgreement Context triple: [Abyei, mentionedInAgreement, Comprehensive Peace Agreement]
-
A.
involvedAgreement
chosen
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
B.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
D.
formedByAgreementWith
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
E.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.