Triple
T19875649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebanon and Israel |
E477628
|
entity |
| Predicate | havePeaceTreaty |
P2504
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Lebanon and Israel, havePeaceTreaty, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePeaceTreaty Context triple: [Lebanon and Israel, havePeaceTreaty, no]
-
A.
peaceTreatySigned
chosen
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
B.
peaceTreatyBetween
Indicates a formal agreement establishing peace or ending conflict between two or more parties.
-
C.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
-
D.
treatyEndedConflict
Indicates that a formal treaty brought an existing conflict between parties to an official end.
-
E.
hasTreatySettlementWith
Indicates the existence of a formal treaty-based agreement or settlement between two 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658db058c8190b7bf0b003ead5bfc |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.