Triple

T685267
Position Surface form Disambiguated ID Type / Status
Subject Gorskie Yevrei E13270 entity
Predicate alsoKnownAs P39 FINISHED
Object Juhurim E18991 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: Juhurim | Statement: [Gorskie Yevrei, alsoKnownAs, Juhurim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Juhurim
Context triple: [Gorskie Yevrei, alsoKnownAs, Juhurim]
  • A. Juhurim chosen
    Juhurim are a Jewish ethnic group from the eastern and northern Caucasus, particularly Dagestan and Azerbaijan, with their own distinct language (Juhuri) and cultural traditions.
  • B. Jandali
    Jandali is an Arabic family name most notably associated with Abdulfattah Jandali, the biological father of Apple co-founder Steve Jobs.
  • C. Juché
    Juché is an alternative spelling of Juche, the North Korean state ideology centered on self-reliance and the absolute leadership of the Kim dynasty.
  • D. Shimsha
    Shimsha is a river in southern India that flows through Karnataka and is known for its waterfalls and contribution to the Kaveri river system.
  • E. Harauti
    Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
  • 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0924dec8190bbbd2bb244f85211 completed March 1, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a67ef349588190b2d4f6177a2f335e completed March 3, 2026, 6:25 a.m.
Created at: March 1, 2026, 7:36 p.m.