Triple
T33925352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | বিনয় |
E869733
|
entity |
| Predicate | সম্পর্ক |
P61561
|
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.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
-
B.
inRelationshipWith
chosen
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
relationshipFocus
Indicates a relationship where particular attention, priority, or emphasis is placed on the connection between two or more entities.
-
D.
closeRelationship
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
-
E.
stateOfRelations
Indicates the current nature or condition of the relationship between two or more entities, such as whether it is friendly, hostile, neutral, or otherwise characterized.
- 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.