Triple
T33925442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | হরান |
E869736
|
entity |
| Predicate | কাহিনিতে_কার্য |
P178126
|
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.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
B.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
C.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
D.
narrativeSettingOfWork
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
E.
شرحه
Indicates that one entity explains, interprets, or clarifies something to another entity.
- F. None of above. chosen
Provenance (4 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_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:49 a.m.