Triple
T25653666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindus in Bengal |
E643169
|
entity |
| Predicate | minorityLocation |
P158963
|
FINISHED |
| Object | Bangladesh |
—
|
NE NERFINISHED |
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: Bangladesh | Statement: [Hindus in Bengal, minorityLocation, Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorityLocation Context triple: [Hindus in Bengal, minorityLocation, Bangladesh]
-
A.
isMinorityTownIn
Indicates that a town is located within a larger region or jurisdiction where it is classified as a minority community.
-
B.
shareMinorityPopulations
Indicates that two entities have overlapping or similar minority population groups in terms of presence, composition, or distribution.
-
C.
minorityGroups
Indicates that the subject is classified as belonging to one or more groups that are numerically, politically, or socially underrepresented or disadvantaged within a larger population.
-
D.
minority
Indicates that one entity belongs to a smaller, less represented, or non-dominant group within a larger population or context.
-
E.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
- F. None of above. chosen
Provenance (4 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_69f5fae906108190af97edeac20f8140 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 6:30 p.m.