Triple

T7955414
Position Surface form Disambiguated ID Type / Status
Subject Tribe of Benjamin E184721 entity
Predicate territoryIncludes P285 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: [Tribe of Benjamin, territoryIncludes, Gibeah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gibeah
Context triple: [Tribe of Benjamin, territoryIncludes, 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. Bethal
    Bethal is a small town in Mpumalanga, South Africa, known historically for its role in the region’s coal mining and agriculture.
  • D. Adullam region
    The Adullam region is a hilly agricultural and historical area in central Israel, known for its vineyards, natural landscapes, and archaeological sites.
  • E. Shechem
    Shechem was an important ancient city in the central highlands of Canaan, serving as a significant political and religious center in biblical times.
  • 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_69ca8292cba881908a64427b938dac47 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b60e9508190ad9974ad551bcbc6 completed March 31, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe0687cdc81909d31e1d964639f36 completed March 31, 2026, 2:55 p.m.
Created at: March 30, 2026, 5:11 p.m.