Triple
T5558366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teves |
E145703
|
entity |
| Predicate | religiousCalendarType |
P38467
|
FINISHED |
| Object | Hebrew religious year |
—
|
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: Hebrew religious year | Statement: [Teves, religiousCalendarType, Hebrew religious year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCalendarType Context triple: [Teves, religiousCalendarType, Hebrew religious year]
-
A.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
-
B.
religiousCalendarRole
Indicates a role or function that something or someone has within a religious calendar, such as marking, organizing, or defining religious dates or observances.
-
C.
liturgicalCalendarType
chosen
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
D.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
E.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201529a88190bf0135e032b048ea |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.