Triple
T31669365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhumij people |
E808227
|
entity |
| Predicate | recognizedAsSTIn |
P185965
|
FINISHED |
| Object | Jharkhand |
—
|
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: Jharkhand | Statement: [Bhumij people, recognizedAsSTIn, Jharkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsSTIn Context triple: [Bhumij people, recognizedAsSTIn, Jharkhand]
-
A.
recognizedAsSTInIndia
chosen
Indicates that an entity is officially acknowledged or designated as a Scheduled Tribe (ST) within the legal and administrative framework of India.
-
B.
recognizedBySomeStatesAs
Indicates that an entity is officially acknowledged or accepted in a particular status or capacity by at least some, but not necessarily all, states.
-
C.
recognizedAsProvinceBy
Indicates that an entity is officially acknowledged or designated as a province by another specified authority or entity.
-
D.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
E.
struckStateOrTerritory
Indicates that an entity has been officially removed, invalidated, or excluded within a particular state or territory.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 30, 2026, 11 p.m.