Triple
T26210890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho people |
E655483
|
entity |
| Predicate | majorTribalGroupOf |
P97190
|
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: [Ho people, majorTribalGroupOf, Jharkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTribalGroupOf Context triple: [Ho people, majorTribalGroupOf, Jharkhand]
-
A.
recognizedTribalGroups
Indicates that certain tribal groups are officially acknowledged or granted formal recognition by an authority or governing body.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
D.
tribeConfederation
Indicates a relationship where multiple tribes are united or organized together into a larger confederated group or alliance.
-
E.
broaderIndigenousGrouping
chosen
Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 8:52 p.m.