Triple

T3611210
Position Surface form Disambiguated ID Type / Status
Subject Hamutal E76490 entity
Predicate origin P410 FINISHED
Object Libnah E67410 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: Libnah | Statement: [Hamutal, origin, Libnah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Libnah
Context triple: [Hamutal, origin, Libnah]
  • A. Libnah chosen
    Libnah was a woman of the royal family of Judah, known primarily as the wife of King Josiah and the mother of King Zedekiah.
  • 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. Kfar Nahum
    Kfar Nahum is the modern Israeli site identified with the ancient fishing village of Capernaum on the northwestern shore of the Sea of Galilee, known for its significant New Testament associations.
  • D. Mappah
    Mappah is a halachic work by Rabbi Moshe Isserles that supplements and adapts the Shulchan Aruch to Ashkenazi Jewish legal customs.
  • E. Ramah
    Ramah is an ancient town in the central highlands of Israel, frequently mentioned in the Hebrew Bible for its strategic location and association with several key prophetic and historical events.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc22cac3c8190bc5f7c45d31668c1 completed March 8, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b433136c94819099bc1d3846e54b07 completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:23 p.m.