Triple
T25631001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday of All Saints |
E642574
|
entity |
| Predicate | hasProperHymnody |
P60491
|
FINISHED |
| Object | troparia |
—
|
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: troparia | Statement: [Sunday of All Saints, hasProperHymnody, troparia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperHymnody Context triple: [Sunday of All Saints, hasProperHymnody, troparia]
-
A.
associatedWithHymns
chosen
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
B.
hasCanticle
Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
-
C.
hymnsPreservedIn
Indicates that specific hymns have been preserved or transmitted within a particular source, collection, or medium.
-
D.
hymnsDedicatedTo
Indicates that certain hymns are specifically devoted or addressed to a particular entity as their subject or object of veneration.
-
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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 21, 2026, 5:18 p.m.