Triple
T3072453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shushan Purim |
E64054
|
entity |
| Predicate | observanceInLeapYear |
P16940
|
FINISHED |
| Object | 15 Adar II in leap years |
—
|
LITERAL 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: 15 Adar II in leap years | Statement: [Shushan Purim, observanceInLeapYear, 15 Adar II in leap years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceInLeapYear Context triple: [Shushan Purim, observanceInLeapYear, 15 Adar II in leap years]
-
A.
observanceMayVaryByYear
Indicates that the way an observance is recognized, scheduled, or practiced can differ from one year to another.
-
B.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
C.
hasDayCountLeapYear
Indicates that the associated day count value applies specifically to a leap year.
-
D.
followsMonthInLeapYears
Indicates that one month directly succeeds another specifically in the context of leap years.
-
E.
occursAfterLeapMonthInLeapYears
chosen
Indicates that the referenced event or time period takes place after the leap month specifically in years that are designated as leap years.
- F. None of above.
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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.