Triple
T31136708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumla district |
E793664
|
entity |
| Predicate | tribalCommunities |
P70068
|
FINISHED |
| Object | Oraon |
—
|
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: Oraon | Statement: [Gumla district, tribalCommunities, Oraon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalCommunities Context triple: [Gumla district, tribalCommunities, Oraon]
-
A.
hasTribalCommunities
chosen
Indicates that an entity possesses, includes, or is associated with one or more tribal communities.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
indigenousCommunity
Indicates that an entity is an indigenous community, i.e., a group with historical, cultural, and ancestral ties to a specific territory predating external or colonial societies.
-
D.
ethnicOrTribalBase
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
E.
tribalEnterprise
Indicates that an entity is a business or commercial venture owned, controlled, or operated by a tribal nation or its governing body.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:05 p.m.