Triple
T26978668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradosh Chandra Mitter |
E679531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bengali fictional character |
C52323
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Bengali fictional character Context triple: [Pradosh Chandra Mitter, instanceOf, Bengali fictional character]
-
A.
Bengali cinema character
A Bengali cinema character is a fictional persona crafted within Bengali-language films, reflecting the region’s cultural, social, and emotional narratives through distinctive traits, dialogues, and relationships.
-
B.
Punjabi folklore character
A Punjabi folklore character is a traditional figure from the myths, legends, and oral stories of Punjab, embodying the region’s cultural values, history, and moral lessons.
-
C.
Punjabi literary character
A Punjabi literary character is a fictional or dramatized figure rooted in the language, culture, and social realities of Punjab, created within Punjabi literature to embody its themes, values, and conflicts.
-
D.
Bengali person
A Bengali person is an individual who identifies with the Bengali ethnic group, typically associated with the Bengali language and the cultural, historical, and social traditions of the Bengal region spanning present-day Bangladesh and the Indian state of West Bengal.
-
E.
Bengali science fiction story
A Bengali science fiction story is a narrative written in the Bengali language that explores speculative scientific, technological, or futuristic concepts within cultural, social, or philosophical contexts rooted in Bengali experience.
- F. None of above. chosen
Provenance (1 batch)
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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:44 a.m.