Triple
T23162162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmar people |
E578614
|
entity |
| Predicate | recognizedAsTribeInIndia |
P21960
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Hmar people, recognizedAsTribeInIndia, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsTribeInIndia Context triple: [Hmar people, recognizedAsTribeInIndia, Yes]
-
A.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
B.
recognizedTribe
chosen
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
C.
stateRecognizedTribe
Indicates that a tribe is officially acknowledged and recognized by a state government as a tribal entity.
-
D.
recognizedAsIndigenousPeopleBy
Indicates that one party formally acknowledges and accepts another party as belonging to an indigenous people or community.
-
E.
recognizedTribalEntity
Indicates that an entity is officially acknowledged as a tribal nation or community by a governing authority.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f019cd881908e3c68d99454da2a |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.