Triple

T19784910
Position Surface form Disambiguated ID Type / Status
Subject siege of Abel Beth Maacah E475235 entity
Predicate instanceOf P0 FINISHED
Object event in the Books of Samuel C16508 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: event in the Books of Samuel
Context triple: [siege of Abel Beth Maacah, instanceOf, event in the Books of Samuel]
  • A. event in the Hebrew Bible chosen
    An event in the Hebrew Bible is a narrated occurrence—historical, theological, or symbolic—in which God’s purposes unfold through actions, experiences, or interventions in the lives of individuals or communities.
  • B. narrative unit in the Books of Samuel
    A narrative unit in the Books of Samuel is a coherent, self-contained segment of the text that presents a specific episode, event, or development in the larger story of Israel’s transition from judges to monarchy.
  • C. event in ancient history
    An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
  • D. event in A Song of Ice and Fire
    An event in A Song of Ice and Fire is a significant occurrence—such as a battle, feast, journey, or political maneuver—that alters the relationships, power dynamics, or fates of characters within the narrative’s historical and geographic context.
  • E. event in the Saur Revolution
    An event in the Saur Revolution is a specific, historically significant occurrence—such as a coup, protest, policy change, or violent confrontation—that took place during the 1978 communist takeover in Afghanistan and contributed to its political, social, or military trajectory.
  • 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_69d8e51b014081908b263e167370529a completed April 10, 2026, 11:55 a.m.
Created at: April 10, 2026, 1:49 p.m.