Triple
T2613996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barwani |
E58841
|
entity |
| Predicate | hasNearbyTribalPopulation |
P34576
|
FINISHED |
| Object | Bhils and other tribal communities |
—
|
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: Bhils and other tribal communities | Statement: [Barwani, hasNearbyTribalPopulation, Bhils and other tribal communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTribalPopulation Context triple: [Barwani, hasNearbyTribalPopulation, Bhils and other tribal communities]
-
A.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
-
B.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
C.
hasTribalMembersFrom
chosen
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
D.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
E.
nearestInhabitedTerritory
Indicates that one territory is the closest inhabited territory to another specified location 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.