Triple
T33925450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | হরান |
E869736
|
entity |
| Predicate | উল্লেখযোগ্যতা |
P22
|
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.
worthyOf
Indicates that one entity deserves, merits, or is suitably qualified for another entity, such as an honor, reward, status, or treatment.
-
B.
notableCriterion
Indicates that something is distinguished or recognized based on a particular standard, measure, or qualifying condition.
-
C.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableOrdinary
Indicates that an entity is notable or significant despite being otherwise ordinary or typical in its category.
-
E.
notableImpression
Indicates that one entity has made a significant or memorable impact on 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_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.