Triple
T33925435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | হরান |
E869736
|
entity |
| Predicate | বিষয়গত_প্রেক্ষাপট |
P2919
|
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.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
B.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
C.
subjectOfEvent
Indicates that an entity participates in or is involved in a particular event as one of its primary actors or focal points.
-
D.
betreft
Indicates that something concerns, relates to, or is about something or someone.
-
E.
basedOnSubject
Indicates that something is derived from, influenced by, or determined according to a particular subject.
- 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:49 a.m.