Triple
T530200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sivan |
E12204
|
entity |
| Predicate | religiousCalendarRole |
P16473
|
FINISHED |
| Object | month of the Torah giving |
—
|
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: month of the Torah giving | Statement: [Sivan, religiousCalendarRole, month of the Torah giving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCalendarRole Context triple: [Sivan, religiousCalendarRole, month of the Torah giving]
-
A.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
C.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
D.
dateInRomanCatholicChurch
Indicates that a specific date is recognized, observed, or used within the context of the Roman Catholic Church’s liturgical or ecclesiastical calendar.
-
E.
religiousAdministration
Indicates that one entity holds authority or responsibility for managing, overseeing, or governing the religious affairs, practices, or institutions of another entity.
- F. None of above. chosen
Provenance (4 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.