Triple
T11928866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhagat Trilochan |
E283857
|
entity |
| Predicate | themeOfHymns |
P11561
|
FINISHED |
| Object | critique of hypocrisy |
—
|
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: critique of hypocrisy | Statement: [Bhagat Trilochan, themeOfHymns, critique of hypocrisy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfHymns Context triple: [Bhagat Trilochan, themeOfHymns, critique of hypocrisy]
-
A.
associatedWithHymns
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
B.
liturgicalTheme
chosen
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
C.
scripturalTheme
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
D.
importantHymn
Indicates that a hymn holds significant importance or prominence within a particular religious, cultural, or musical context.
-
E.
hymnsPreservedIn
Indicates that specific hymns have been preserved or transmitted within a particular source, collection, or medium.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903024afc8190a97aa3263dc7d017 |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.