Triple

T2102244
Position Surface form Disambiguated ID Type / Status
Subject Ancient Israel E37114 entity
Predicate keyCity P235 FINISHED
Object Shechem E80189 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: Shechem | Statement: [Ancient Israel, keyCity, Shechem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shechem
Context triple: [Ancient Israel, keyCity, Shechem]
  • A. Shechem chosen
    Shechem was an important ancient city in the central highlands of Canaan, serving as a significant political and religious center in biblical times.
  • B. Riblah
    Riblah was an ancient town in Syria that served as a strategic military and administrative headquarters, notably used by the Babylonian king Nebuchadnezzar during the final conquest of Judah.
  • C. Gibeah
    Gibeah was an ancient Israelite city in the territory of Benjamin, historically notable as the royal seat of King Saul.
  • D. Beersheba
    Beersheba is a major city in southern Israel, often regarded as the "Capital of the Negev" and known for its historical significance and rapid modern development.
  • E. Yokneam Illit
    Yokneam Illit is a city in northern Israel known for its high-tech industrial parks and rapid development from a small town into a regional technology hub.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabc83a8819091f786f21d33b5a6 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae3068189c81909cf76fd1fc2a0fe6 completed March 9, 2026, 2:28 a.m.
Created at: March 4, 2026, 7:43 p.m.