Triple
T23987574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel and Egypt |
E604979
|
entity |
| Predicate | peaceAccordsYear |
P23330
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [Israel and Egypt, peaceAccordsYear, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peaceAccordsYear Context triple: [Israel and Egypt, peaceAccordsYear, 1978]
-
A.
peaceAccordDate
Indicates the date on which a formal peace accord between parties was signed or came into effect.
-
B.
hasPeaceAccord
Indicates that a formal peace agreement or treaty exists between the related entities, establishing terms to end or prevent conflict.
-
C.
peaceSignedAt
Indicates that a formal peace agreement was signed at a specific location.
-
D.
treatySignedYear
chosen
Indicates the calendar year in which a specific treaty was formally signed.
-
E.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38838f481909a52fccd392a92df |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:36 p.m.