Triple
T11519927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massabielle Grotto |
E273134
|
entity |
| Predicate | mainFeastDay |
P27473
|
FINISHED |
| Object | 11 February |
—
|
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: 11 February | Statement: [Massabielle Grotto, mainFeastDay, 11 February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFeastDay Context triple: [Massabielle Grotto, mainFeastDay, 11 February]
-
A.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
B.
feastDayObservedOn
chosen
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
C.
liturgicalFeastDay
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
D.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
E.
feastDayHonors
Indicates that a particular feast day is dedicated to honoring or commemorating a specific person, group, or event.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fcf927081908ef89eff7ad833b0 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.