Triple
T24411694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Maria Presentatiekerk (Ommel) |
E615466
|
entity |
| Predicate | hasMarianDevotionType |
P107974
|
FINISHED |
| Object | Marian pilgrimage |
—
|
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: Marian pilgrimage | Statement: [St. Maria Presentatiekerk (Ommel), hasMarianDevotionType, Marian pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarianDevotionType Context triple: [St. Maria Presentatiekerk (Ommel), hasMarianDevotionType, Marian pilgrimage]
-
A.
hasMarianDedication
chosen
Indicates that something (typically a church, chapel, or shrine) is dedicated to or in honor of the Virgin Mary.
-
B.
hasDevoteeType
Indicates that an entity has a devotee characterized by a specific type or category of devotion.
-
C.
hasMonthOfSpecialDevotion
Indicates that there is a specific month associated with a special religious or spiritual devotion related to the subject.
-
D.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
E.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958241e48190ae33297c5c5c0e59 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:09 a.m.