Triple
T24421064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaritan calendar |
E615723
|
entity |
| Predicate | calendarClass |
P66056
|
FINISHED |
| Object | religious festival calendar |
—
|
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: religious festival calendar | Statement: [Samaritan calendar, calendarClass, religious festival calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarClass Context triple: [Samaritan calendar, calendarClass, religious festival calendar]
-
A.
calendarCategory
chosen
Indicates the classification or grouping assigned to calendar entries based on their type, purpose, or context.
-
B.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
C.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
D.
calendarContribution
Indicates a relationship where an entity adds to, modifies, or otherwise participates in the creation or maintenance of a calendar or scheduled events.
-
E.
calendarAssociation
Indicates a relationship where one entity is linked to or associated with a particular calendar or calendaring context (such as events, schedules, or timeframes).
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a34d3081908d6099365e2e4046 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.