Triple

T3654697
Position Surface form Disambiguated ID Type / Status
Subject Canaanites E77501 entity
Predicate region P40 FINISHED
Object Canaan E14440 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: Canaan | Statement: [Canaanites, region, Canaan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Canaan
Context triple: [Canaanites, region, Canaan]
  • A. Canaan chosen
    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.
  • B. Cannan
    Cannan is a surname of English origin borne by various notable individuals, including politicians, writers, and public figures.
  • 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. 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.
  • E. Canaanites
    The Canaanites were an ancient Semitic-speaking people of the Levant known from Bronze Age city-states and frequently mentioned in biblical and Near Eastern sources.
  • 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_69ad85def5cc8190863dccf55a18bebb completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc3b9164c81908938a4338430d193 completed March 8, 2026, 6:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4883bb50c8190bd383b21ac748a2e completed March 13, 2026, 9:57 p.m.
Created at: March 8, 2026, 3:24 p.m.