Triple
T35184778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of the Roses |
E1015954
|
entity |
| Predicate | hasFeastOrCommemorativeDays |
P44757
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Our Lady of the Roses, hasFeastOrCommemorativeDays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastOrCommemorativeDays Context triple: [Our Lady of the Roses, hasFeastOrCommemorativeDays, yes]
-
A.
hasFeastOrCommemoration
chosen
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
B.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
C.
hasImportantHoliday
Indicates that an entity is associated with a holiday considered significant or special in some context.
-
D.
hasLocalFeastMonth
Indicates that a particular location or community observes a local feast or festival during a specified month.
-
E.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:02 p.m.