Triple

T4359988
Position Surface form Disambiguated ID Type / Status
Subject Shfela E98638 entity
Predicate contains P35 FINISHED
Object Tel Lachish E233624 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: Tel Lachish | Statement: [Shfela, contains, Tel Lachish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tel Lachish
Context triple: [Shfela, contains, Tel Lachish]
  • A. Lachish chosen
    Lachish was a major fortified Canaanite and later Judahite city in the Shephelah region, known as a strategic military and administrative center in ancient Israel.
  • B. Sha'ar Shechem
    Sha'ar Shechem is the Hebrew name for Damascus Gate, one of the main historic entrances to Jerusalem’s Old City, notable for its large stone archway and bustling marketplace.
  • C. Sha'ar Yafo
    Sha'ar Yafo is the Hebrew name for Jaffa Gate, one of the main historic entrances to Jerusalem’s Old City.
  • D. Hazor
    Hazor was an important ancient Canaanite city-state in northern Israel, known as one of the largest and most influential urban centers in the Levant during the Bronze and Iron Ages.
  • E. Gezerot
    Gezerot are rabbinic decrees in Judaism enacted as protective safeguards around biblical law or to address communal needs.
  • 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_69b3454c772081908e20173e379e8ebe completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351e3220881909dc9d02ab024abf5 completed March 12, 2026, 11:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5e501671c8190bf8a9998f46a9f3b completed March 14, 2026, 10:45 p.m.
Created at: March 12, 2026, 11:16 p.m.