Triple
T31692808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goula |
E808836
|
entity |
| Predicate | prominentUsage |
P5773
|
FINISHED |
| Object | bhakti (devotional) themes |
—
|
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: bhakti (devotional) themes | Statement: [Goula, prominentUsage, bhakti (devotional) themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentUsage Context triple: [Goula, prominentUsage, bhakti (devotional) themes]
-
A.
notableUse
chosen
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
adoptedProminentlyBy
Indicates that something (such as an idea, practice, or technology) has been widely and visibly taken up or embraced by a particular group or entity.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
firstProminentUse
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
-
E.
promotesUseIn
Indicates that one entity actively encourages, supports, or increases the adoption or application of another entity within a particular context or setting.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:09 p.m.