Triple
T113491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew calendar |
E2294
|
entity |
| Predicate | hasMonth |
P6433
|
FINISHED |
| Object | Adar II |
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 II | Statement: [Hebrew calendar, hasMonth, Adar II]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adar II Context triple: [Hebrew calendar, hasMonth, Adar II]
-
A.
Adar
Adar is the twelfth month of the Hebrew calendar, traditionally associated with the festival of Purim and themes of joy and celebration.
-
B.
Adar I
chosen
Adar I is the leap-year intercalary month added to the Hebrew calendar before the regular month of Adar.
-
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.
Tevet
Tevet is a winter month in the Hebrew calendar, typically falling in December–January and associated with several Jewish fasts and historical commemorations.
-
E.
Nisan
Nisan is the first month of the Hebrew religious year, traditionally associated with spring and the festival of Passover.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25b800d08819099a44429d5c82c68 |
completed | Feb. 28, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2bf67902c8190b4e88c70d25439e8 |
completed | Feb. 28, 2026, 10:11 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.