Triple
T30493153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibang Biosphere Reserve |
E775923
|
entity |
| Predicate | inhabitedByCommunity |
P6481
|
FINISHED |
| Object | indigenous 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: indigenous communities | Statement: [Dibang Biosphere Reserve, inhabitedByCommunity, indigenous communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedByCommunity Context triple: [Dibang Biosphere Reserve, inhabitedByCommunity, indigenous communities]
-
A.
inhabitedBy
chosen
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
B.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
C.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
D.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
E.
governedCommunity
Indicates that one entity exercises governing authority or administrative control over a community or group of people.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68775ebd081908706784fe8f8fdf8 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:14 p.m.