Triple
T35884958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schoenstatt Movement |
E1037615
|
entity |
| Predicate | hasCentralDevotionTo |
P77744
|
FINISHED |
| Object | Blessed Virgin Mary |
—
|
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: Blessed Virgin Mary | Statement: [Schoenstatt Movement, hasCentralDevotionTo, Blessed Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralDevotionTo Context triple: [Schoenstatt Movement, hasCentralDevotionTo, Blessed Virgin Mary]
-
A.
isDevotedTo
chosen
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
B.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
C.
isWorshippedFor
Indicates that one entity is revered or honored by another specifically because of a particular quality, deed, or attribute.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:06 p.m.