Triple

T6173441
Position Surface form Disambiguated ID Type / Status
Subject HaMechaber E137759 entity
Predicate relatedConcept P37 FINISHED
Object Maran E137758 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: Maran | Statement: [HaMechaber, relatedConcept, Maran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maran
Context triple: [HaMechaber, relatedConcept, Maran]
  • A. Maran chosen
    Maran is an honorific title most famously associated with Rabbi Yosef Karo, the preeminent 16th-century halachic authority and author of the Shulchan Aruch.
  • B. Marrar
    Marrar is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural community and country lifestyle.
  • C. Dror
    Dror was a Jewish underground resistance group associated with the Jewish Combat Organization that took part in anti-Nazi activities during World War II.
  • D. Merari
    Merari is a biblical figure recognized as one of the sons of Levi and the progenitor of the Merarite clan of Levites.
  • E. Dayan
    Dayan is a Hebrew surname most famously associated with Israeli military leader and politician Moshe Dayan.
  • 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_69c008a68c508190a8d78245c865960e completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d94c47481909745b2533926a1ca completed March 22, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c141b200788190bd8d968edba53e5f completed March 23, 2026, 1:35 p.m.
Created at: March 22, 2026, 4:18 p.m.