Triple
T36822489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afterfeast of the Nativity |
E909922
|
entity |
| Predicate | usesHymn |
P60491
|
FINISHED |
| Object | troparion of the Nativity |
—
|
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: troparion of the Nativity | Statement: [Afterfeast of the Nativity, usesHymn, troparion of the Nativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHymn Context triple: [Afterfeast of the Nativity, usesHymn, troparion of the Nativity]
-
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.
usesLiturgicalMelody
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
-
C.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
D.
hymnNumber
Indicates the specific numerical designation assigned to a hymn within a hymnal or song collection.
-
E.
hasCanticle
Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca99aa248190bbd2a01125f61f8c |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.