Triple
T33925371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | পৈরীমোহন |
E869734
|
entity |
| Predicate | গুরুত্ব |
P41499
|
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.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
B.
وزن
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
C.
hasParticularSignificanceFor
chosen
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
D.
भूमिका
Indicates a relationship where an entity serves, functions, or acts in a particular capacity or role with respect to another entity or context.
-
E.
उपाधि
Indicates that an entity holds or is designated by a particular title, rank, or honorific.
- 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.