Triple
T1243730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Beggar in Jerusalem |
E26715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | literary work about the Six-Day War |
C4035
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: literary work about the Six-Day War Context triple: [A Beggar in Jerusalem, instanceOf, literary work about the Six-Day War]
-
A.
post–Yom Kippur War diplomacy
Post–Yom Kippur War diplomacy refers to the series of negotiations, shuttle missions, and agreements among Israel, Egypt, Syria, the United States, and other actors after the 1973 war that reshaped Middle Eastern borders, security arrangements, and great-power influence in the region.
-
B.
Jewish historical work
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
-
C.
literaryWork
chosen
A literaryWork is a created written or spoken artistic composition, such as a novel, poem, or play, that conveys ideas, stories, or emotions through language.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
E.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
- F. None of above.
Provenance (1 batch)
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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.