Triple
T19814202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurmi community |
E476018
|
entity |
| Predicate | casteCategoryInMadhyaPradesh |
P137423
|
FINISHED |
| Object | OBC |
—
|
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: OBC | Statement: [Kurmi community, casteCategoryInMadhyaPradesh, OBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casteCategoryInMadhyaPradesh Context triple: [Kurmi community, casteCategoryInMadhyaPradesh, OBC]
-
A.
hasCasteSystem
Indicates that a society or group is organized into a hierarchical caste system that assigns people to fixed social strata.
-
B.
relationToJanaGanaMana
Indicates a relationship or association that something has with the Indian national anthem "Jana Gana Mana," such as being about it, derived from it, or otherwise connected to it.
-
C.
rankByPopulationInIndia
Indicates the relative ordering of entities based on their population size within India.
-
D.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
E.
hasCouncilAreaCode
Indicates that an entity is associated with a specific council area identified by a particular code.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654f6495c81908e7eea359a60e40f |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.