Triple
T25656221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | জব্বার |
E643242
|
entity |
| Predicate | নামের_ধর্মীয়_পরিচিতি |
P146129
|
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.
religiousNamesake
Indicates that one entity serves as the religiously significant figure, concept, or object after which the other entity is named.
-
B.
hasReligiousName
chosen
Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
-
C.
hasReligiousAffiliationInName
Indicates that an entity’s name explicitly includes or reflects a religious affiliation or association.
-
D.
hasNameInReligionOrFolklore
Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
-
E.
religiousName
Indicates that an entity has or is known by a name specifically associated with a religious role, identity, or context.
- 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_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 6:33 p.m.