Triple
T7373648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autonomous Region of Bougainville |
E170069
|
entity |
| Predicate | peaceAgreementSigned |
P31618
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Autonomous Region of Bougainville, peaceAgreementSigned, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peaceAgreementSigned Context triple: [Autonomous Region of Bougainville, peaceAgreementSigned, 2001]
-
A.
peaceSignedAt
Indicates that a formal peace agreement was signed at a specific location.
-
B.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
C.
peaceAccordDate
chosen
Indicates the date on which a formal peace accord between parties was signed or came into effect.
-
D.
peaceTerms
Indicates the conditions or agreements proposed or accepted by parties to establish or maintain peace after or during a conflict.
-
E.
peaceProcessInvolved
Indicates that an entity participates in, contributes to, or is otherwise involved in a formal peace process or peace negotiations.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a50898819087097a64e09e19eb |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.