Triple
T33925448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | হরান |
E869736
|
entity |
| Predicate | ধর্মীয়_প্রেক্ষাপট |
P9028
|
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.
أصل_ديني
Indicates a religious origin or affiliation that an entity belongs to or is derived from.
-
B.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
C.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
- 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_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.