Triple
T28510784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Solitude |
E721476
|
entity |
| Predicate | hasDevotionalTheme |
P189715
|
FINISHED |
| Object | sorrow |
—
|
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: sorrow | Statement: [Our Lady of Solitude, hasDevotionalTheme, sorrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotionalTheme Context triple: [Our Lady of Solitude, hasDevotionalTheme, sorrow]
-
A.
hasDevotionalForm
Indicates that one entity takes or possesses a devotional expression, format, or mode in relation to another entity or context.
-
B.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
C.
hasDevotionalImpact
Indicates that something influences, deepens, or shapes another entity’s devotional or spiritual practice or attitude.
-
D.
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).
-
E.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
- F. None of above. chosen
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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 28, 2026, 3:12 a.m.