Triple

T4887572
Position Surface form Disambiguated ID Type / Status
Subject Saul E109473 entity
Predicate associatedWith P37 FINISHED
Object Gibeah E68812 NE 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: Gibeah | Statement: [Saul, associatedWith, Gibeah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gibeah
Context triple: [Saul, associatedWith, Gibeah]
  • A. Gibeah chosen
    Gibeah was an ancient Israelite city in the territory of Benjamin, historically notable as the royal seat of King Saul.
  • B. Kedesh
    Kedesh was an ancient city in the territory of the Israelite tribe of Naphtali, known as a Levitical city of refuge in the Hebrew Bible.
  • C. Adullam region
    The Adullam region is a hilly agricultural and historical area in central Israel, known for its vineyards, natural landscapes, and archaeological sites.
  • D. Shechem
    Shechem was an important ancient city in the central highlands of Canaan, serving as a significant political and religious center in biblical times.
  • E. Anathoth
    Anathoth is an ancient Levitical town in the territory of Benjamin, mentioned in the Hebrew Bible and traditionally associated with the prophet Jeremiah.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd440f71348190b99938e59fb7f9a1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e03a7fc8190bcac63f4b19e586e completed March 20, 2026, 3:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6fbba1688190a812cac53992dece completed March 21, 2026, 10:15 a.m.
Created at: March 20, 2026, 1:28 p.m.