Triple
T33925444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | হরান |
E869736
|
entity |
| Predicate | সাহিত্যিক_তাৎপর্য |
P27711
|
FINISHED |
| Object | চরিত্রের মানসিক বিকাশের প্রতীক |
—
|
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: চরিত্রের মানসিক বিকাশের প্রতীক | Statement: [হরান, সাহিত্যিক_তাৎপর্য, চরিত্রের মানসিক বিকাশের প্রতীক]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: সাহিত্যিক_তাৎপর্য Context triple: [হরান, সাহিত্যিক_তাৎপর্য, চরিত্রের মানসিক বিকাশের প্রতীক]
-
A.
literaryUse
Indicates that something is employed or referenced within a literary context, such as in a written work, style, or technique.
-
B.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
D.
inLiterature
chosen
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
E.
literaryCritic
Indicates a relationship where one entity evaluates, analyzes, or interprets the literary works or writings of 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:49 a.m.