Triple
T34015316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Ettal |
E872224
|
entity |
| Predicate | hasDevotionForm |
P129877
|
FINISHED |
| Object | Marian devotion |
—
|
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 devotion | Statement: [Our Lady of Ettal, hasDevotionForm, Marian devotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotionForm Context triple: [Our Lady of Ettal, hasDevotionForm, Marian devotion]
-
A.
hasDevotionalForm
chosen
Indicates that one entity takes or possesses a devotional expression, format, or mode in relation to another entity or context.
-
B.
hasDevotionalFormula
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
-
C.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
D.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
-
E.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:51 a.m.