Triple
T26893208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | মেঘনাদবধ কাব্য |
E677829
|
entity |
| Predicate | hasHeroicDeathOf |
P41523
|
FINISHED |
| Object | মেঘনাদ |
—
|
NE NERFINISHED |
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: [মেঘনাদবধ কাব্য, hasHeroicDeathOf, মেঘনাদ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroicDeathOf Context triple: [মেঘনাদবধ কাব্য, hasHeroicDeathOf, মেঘনাদ]
-
A.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
B.
legendaryDeath
chosen
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
C.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
D.
hasRankAtDeath
Indicates the rank or position an entity held at the time of its death.
-
E.
hasDeathGod
Indicates that an entity is associated with, served by, or under the dominion of a specific deity or supernatural being of death.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 5:46 a.m.