Triple
T25656205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | জব্বার |
E643242
|
entity |
| Predicate | ব্যবহারকারী_সম্প্রদায় |
P94060
|
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.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
B.
scriptUserCommunity
chosen
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
C.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
D.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
E.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faebdbf08190ab8856d10be8abd1 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:33 p.m.