Triple
T6909493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egypt–Israel relations |
E159893
|
entity |
| Predicate | ArabLeagueStatusOfEgyptAfterTreaty |
P74081
|
FINISHED |
| Object | suspended |
—
|
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: suspended | Statement: [Egypt–Israel relations, ArabLeagueStatusOfEgyptAfterTreaty, suspended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ArabLeagueStatusOfEgyptAfterTreaty Context triple: [Egypt–Israel relations, ArabLeagueStatusOfEgyptAfterTreaty, suspended]
-
A.
joinedArabLeague
Indicates that an entity became a member state of the Arab League.
-
B.
ArabPeaceInitiativeAdoptionYear
Indicates the year in which an entity formally adopted or endorsed the Arab Peace Initiative.
-
C.
statusInEgypt
Indicates the legal, social, or official condition or standing that an entity holds specifically within the context of Egypt.
-
D.
statusOfArmistice
Indicates the current condition or standing of an armistice agreement between parties.
-
E.
treatyRelatedToDissolution
Indicates that a treaty is connected to, concerns, or results in the dissolution or termination of a political, legal, or organizational entity.
- F. None of above. chosen
Provenance (4 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c00e948190b103a2b2a2738bb1 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.