Triple

T2998677
Position Surface form Disambiguated ID Type / Status
Subject Purim Katan E81132 entity
Predicate occursInMonth P1167 FINISHED
Object Adar I E16733 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: Adar I | Statement: [Purim Katan, occursInMonth, Adar I]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adar I
Context triple: [Purim Katan, occursInMonth, Adar I]
  • A. Adar I chosen
    Adar I is the leap-year intercalary month added to the Hebrew calendar before the regular month of Adar.
  • B. Adar
    Adar is the twelfth month of the Hebrew calendar, traditionally associated with the festival of Purim and themes of joy and celebration.
  • C. Sivan
    Sivan is the third month of the Hebrew calendar, traditionally associated with the festival of Shavuot and the giving of the Torah.
  • D. Malchi-shua
    Malchi-shua was one of King Saul’s sons, a Hebrew prince mentioned in the Bible who died alongside his father in battle against the Philistines.
  • E. Berechiah
    Berechiah is a biblical figure mentioned in the Hebrew Bible as part of the priestly and prophetic lineage associated with the prophet Zechariah.
  • 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_69ad8b187fc8819085914d3c9ea3142d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99f766408190a5591efce8346bb9 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e468db4819094fb7badbd48ce1e completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 2:59 p.m.