Triple
T34589890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation of the Blessed Virgin Mary |
E888148
|
entity |
| Predicate | scripturalCanticle |
P63157
|
FINISHED |
| Object | Magnificat |
—
|
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: Magnificat | Statement: [Visitation of the Blessed Virgin Mary, scripturalCanticle, Magnificat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalCanticle Context triple: [Visitation of the Blessed Virgin Mary, scripturalCanticle, Magnificat]
-
A.
hasCanticle
chosen
Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
-
B.
notableChant
Indicates that an entity is recognized for having a distinctive or significant chant associated with it.
-
C.
relatedChantOrSong
Indicates that one chant or song is associated with, derived from, or otherwise connected to another chant or song.
-
D.
canonizedScriptureIn
Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
-
E.
usesLiturgicalMelody
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 2:03 a.m.