Triple
T13477488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gush Emunim |
E318284
|
entity |
| Predicate | positionOnCampDavidAccords |
P54133
|
FINISHED |
| Object | Opposed return of Sinai to Egypt |
—
|
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: Opposed return of Sinai to Egypt | Statement: [Gush Emunim, positionOnCampDavidAccords, Opposed return of Sinai to Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCampDavidAccords Context triple: [Gush Emunim, positionOnCampDavidAccords, Opposed return of Sinai to Egypt]
-
A.
positionOnArabIsraeliConflict
chosen
Indicates a stance or viewpoint that an entity holds regarding the Arab–Israeli conflict.
-
B.
positionOnSecurityTreaty
Indicates the stance or viewpoint an entity holds regarding a specific security treaty.
-
C.
positionOnNeutrality
Indicates the stance or viewpoint an entity holds regarding neutrality in a given context (e.g., political, ethical, or diplomatic).
-
D.
positionOnGoodFridayAgreement
Indicates an entity’s stance or viewpoint regarding the Good Friday Agreement.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf266c508190930d30776c09ce35 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.