Triple
T25239364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagri people |
E632419
|
entity |
| Predicate | casteComposition |
P90994
|
FINISHED |
| Object | multi-caste community |
—
|
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: multi-caste community | Statement: [Bagri people, casteComposition, multi-caste community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casteComposition Context triple: [Bagri people, casteComposition, multi-caste community]
-
A.
hasCasteSystem
chosen
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.
racialComposition
Indicates the proportional makeup of different racial groups within a given population or entity.
-
E.
ethnicComponents
Indicates that an entity is composed of, associated with, or characterized by one or more specified ethnic groups or ethnic origins.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47dfd5ec081908e5807a73eaa5a8f |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:07 p.m.