Triple
T24196630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTAC |
E599851
|
entity |
| Predicate | peaceAgreementImplemented |
P133400
|
FINISHED |
| Object | Paris Peace Agreements |
—
|
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: Paris Peace Agreements | Statement: [UNTAC, peaceAgreementImplemented, Paris Peace Agreements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peaceAgreementImplemented Context triple: [UNTAC, peaceAgreementImplemented, Paris Peace Agreements]
-
A.
hasPeaceAccord
Indicates that a formal peace agreement or treaty exists between the related entities, establishing terms to end or prevent conflict.
-
B.
peaceProcessInvolved
Indicates that an entity participates in, contributes to, or is otherwise involved in a formal peace process or peace negotiations.
-
C.
peaceProcessMilestone
Indicates a significant event or achievement marking progress within a broader peace negotiation or conflict-resolution process.
-
D.
peaceAccordDate
Indicates the date on which a formal peace accord between parties was signed or came into effect.
-
E.
treatyImplemented
chosen
Indicates that the terms or provisions of a treaty have been put into effect or carried out in practice between the relevant parties.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24ad83c819084ac9e34d2cc2120 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.