Triple
T37534663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guatemalan peace accords |
E933162
|
entity |
| Predicate | finalAccordSignedOn |
P439
|
FINISHED |
| Object | 1996-12-29 |
—
|
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: 1996-12-29 | Statement: [Guatemalan peace accords, finalAccordSignedOn, 1996-12-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAccordSignedOn Context triple: [Guatemalan peace accords, finalAccordSignedOn, 1996-12-29]
-
A.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
B.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
C.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
D.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.