Triple
T26496537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Le Puy |
E669296
|
entity |
| Predicate | hasMajorPilgrimageSeason |
P32543
|
FINISHED |
| Object | Easter |
—
|
NE NERFINISHED |
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: Easter | Statement: [Our Lady of Le Puy, hasMajorPilgrimageSeason, Easter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPilgrimageSeason Context triple: [Our Lady of Le Puy, hasMajorPilgrimageSeason, Easter]
-
A.
hasPilgrimageOrFeast
Indicates that there is a religious pilgrimage or feast associated with, dedicated to, or occurring in relation to the referenced entity.
-
B.
pilgrimageSeason
chosen
Indicates the time period or season during which religious pilgrimages customarily take place.
-
C.
majorPilgrimageEvent
Indicates a significant religious journey or gathering undertaken by many participants as a central act of devotion or worship.
-
D.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
E.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 1:09 a.m.