Triple
T30227861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champakalata |
E768541
|
entity |
| Predicate | typeOfDevotee |
P141482
|
FINISHED |
| Object | eternal associate of Radha and Krishna |
—
|
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: eternal associate of Radha and Krishna | Statement: [Champakalata, typeOfDevotee, eternal associate of Radha and Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDevotee Context triple: [Champakalata, typeOfDevotee, eternal associate of Radha and Krishna]
-
A.
hasDevoteeType
chosen
Indicates that an entity has a devotee characterized by a specific type or category of devotion.
-
B.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
E.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: April 29, 2026, 7:36 p.m.