Triple

T25061566
Position Surface form Disambiguated ID Type / Status
Subject Season (anti-Irgun campaign) E627671 entity
Predicate instanceOf P0 FINISHED
Object intra-Jewish conflict C49390 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: intra-Jewish conflict
Context triple: [Season (anti-Irgun campaign), instanceOf, intra-Jewish conflict]
  • A. anti-Jewish riot
    An anti-Jewish riot is a violent, collective attack by a non-Jewish population against Jewish individuals, communities, or property, typically fueled by antisemitic prejudice, political tensions, or social unrest.
  • B. Arab–Israeli conflict
    The Arab–Israeli conflict is a long-standing political, territorial, and ideological struggle between Israel and various Arab states and Palestinian groups, centered on competing national claims to the land between the Jordan River and the Mediterranean Sea.
  • C. sectarian conflict
    Sectarian conflict is a form of violence or prolonged tension between groups divided by religious, ethnic, or ideological sects, often rooted in historical grievances and identity-based rivalries.
  • D. civil conflict
    Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
  • E. conflict in the Polish–Lithuanian Commonwealth
    Conflict in the Polish–Lithuanian Commonwealth encompasses the political, social, religious, and military disputes that arose within and around the dual state, shaping its internal dynamics and external relations from its formation to its partitions.
  • F. None of above. chosen

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_69e2ff2c45f48190afa28369f1df6786 completed April 18, 2026, 3:49 a.m.
Created at: April 18, 2026, 6:10 a.m.