Triple
T25653696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindus in Bengal |
E643169
|
entity |
| Predicate | casteStructure |
P104583
|
FINISHED |
| Object | presence of Kayastha castes |
—
|
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: presence of Kayastha castes | Statement: [Hindus in Bengal, casteStructure, presence of Kayastha castes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casteStructure Context triple: [Hindus in Bengal, casteStructure, presence of Kayastha castes]
-
A.
hasCasteSystem
Indicates that a society or group is organized into a hierarchical caste system that assigns people to fixed social strata.
-
B.
hasCaste
Indicates that an entity belongs to or is associated with a particular caste within a social or hierarchical system.
-
C.
casteCategoryInMadhyaPradesh
Indicates that an entity belongs to a specific caste category as officially recognized within the state of Madhya Pradesh.
-
D.
colonyCastes
Indicates a relationship where a colony is organized into distinct social or functional castes or roles.
-
E.
associatedWithCaste
chosen
Indicates a relationship where an entity is linked or connected to a particular caste, typically by social, cultural, or hereditary association.
- 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_69f5fae906108190af97edeac20f8140 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 6:30 p.m.