Triple

T10720509
Position Surface form Disambiguated ID Type / Status
Subject מְדָן E252806 entity
Predicate siblingOf P363 FINISHED
Object מִדְיָן E51335 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: מִדְיָן | Statement: [מְדָן, siblingOf, מִדְיָן]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: מִדְיָן
Context triple: [מְדָן, siblingOf, מִדְיָן]
  • A. Midian chosen
    Midian is a biblical figure regarded as one of Abraham’s sons and traditionally seen as the ancestor of the Midianite people.
  • B. Canaan
    Canaan is the ancient Near Eastern land traditionally associated with the biblical Promised Land, encompassing parts of modern-day Israel, Palestine, Lebanon, and surrounding areas.
  • C. Madyan
    Madyan is a scenic hill town and tourist resort in Pakistan’s Swat Valley, known for its cool climate, river views, and surrounding mountains.
  • D. Midianite
    A Midianite was a member of an ancient Northwest Arabian people mentioned in the Hebrew Bible, traditionally associated with the region east of the Gulf of Aqaba and known for their interactions with the Israelites.
  • E. Edom
    Edom was an ancient kingdom in the southern Levant, traditionally associated with the descendants of Esau and located south of the Kingdom of Judah.
  • 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_69d6aa5d8be481909a43218b2bfdbe95 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d70d42033c81908cafe500213a9da1 completed April 9, 2026, 2:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69e23b436efc819080022105e3f5f2e1 completed April 17, 2026, 1:53 p.m.
Created at: April 8, 2026, 9:13 p.m.