Triple
T8933066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abuja Accord |
E212703
|
entity |
| Predicate | signatoryCategory |
P14945
|
FINISHED |
| Object | Liberian warring factions |
—
|
LITERAL 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: Liberian warring factions | Statement: [Abuja Accord, signatoryCategory, Liberian warring factions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoryCategory Context triple: [Abuja Accord, signatoryCategory, Liberian warring factions]
-
A.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
B.
signType
Indicates the specific category or kind of sign involved in the relationship or action.
-
C.
signatoryState
Indicates that a state is a formal party to, and has signed or ratified, a specific treaty, agreement, or legal instrument.
-
D.
signGivenBy
Indicates that a sign (such as a signal, gesture, or indication) is produced or provided by one entity to another.
-
E.
signatoryBloc
chosen
Indicates that an entity is a member of, or aligned with, a specific bloc or group that has jointly signed or endorsed an agreement, treaty, or document.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668fa87c8190bfeda820368b89e4 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.