Triple
T29186375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaura Nitai |
E739878
|
entity |
| Predicate | liturgicalChant |
P88276
|
FINISHED |
| Object | Hare Krishna maha-mantra |
—
|
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: Hare Krishna maha-mantra | Statement: [Gaura Nitai, liturgicalChant, Hare Krishna maha-mantra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalChant Context triple: [Gaura Nitai, liturgicalChant, Hare Krishna maha-mantra]
-
A.
liturgicalResonance
Indicates a relationship where something echoes, reflects, or aligns with the themes, forms, or atmosphere of liturgical (formal religious) practice.
-
B.
notableChant
Indicates that an entity is recognized for having a distinctive or significant chant associated with it.
-
C.
usesLiturgicalMelody
chosen
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
-
D.
liturgicalGenre
Indicates the specific type or category of liturgical text, music, or ritual to which something belongs.
-
E.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, noon