Triple
T29339548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Saint Luke |
E743998
|
entity |
| Predicate | occursOnSameDateAs |
P15660
|
FINISHED |
| Object | October 18 each 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: October 18 each year | Statement: [Feast of Saint Luke, occursOnSameDateAs, October 18 each year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursOnSameDateAs Context triple: [Feast of Saint Luke, occursOnSameDateAs, October 18 each year]
-
A.
heldOnSameDayAs
chosen
Indicates that two events or occurrences took place on the same calendar day.
-
B.
requiresSameDates
Indicates that the related entities must share identical start and end dates for the associated activity or condition.
-
C.
occursOnOrAround
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
D.
followsSameWeekendAs
Indicates that two time periods share the same weekend dates or fall within the same weekend interval.
-
E.
celebratedOnOrNear
Indicates that one event, occasion, or observance is celebrated on the same date as, or within a close temporal proximity to, another.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 1:33 p.m.