Triple
T34378156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Le Puy-en-Velay |
E882349
|
entity |
| Predicate | hasMarianDevotion |
P107974
|
FINISHED |
| Object | Notre-Dame du Puy |
E177385
|
NE 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: Notre-Dame du Puy | Statement: [Diocese of Le Puy-en-Velay, hasMarianDevotion, Notre-Dame du Puy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarianDevotion Context triple: [Diocese of Le Puy-en-Velay, hasMarianDevotion, Notre-Dame du Puy]
-
A.
hasMarianDedication
chosen
Indicates that something (typically a church, chapel, or shrine) is dedicated to or in honor of the Virgin Mary.
-
B.
venerationOfMary
Indicates a relationship in which an entity shows reverence, honor, or devotional respect toward Mary.
-
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.
hasLiturgicalDevotionType
Indicates a relationship in which a religious practice, observance, or devotion is associated with a specific type or form of liturgical devotion.
- F. None of above.
Provenance (4 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729c7f0a08190b5f3e36b70f226c0 |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 1, 2026, 1:59 a.m.