Triple
T30365883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimasa Kachari community |
E772419
|
entity |
| Predicate | regionOfHistoricalRule |
P136261
|
FINISHED |
| Object | Dima Hasao region |
—
|
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: Dima Hasao region | Statement: [Dimasa Kachari community, regionOfHistoricalRule, Dima Hasao region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfHistoricalRule Context triple: [Dimasa Kachari community, regionOfHistoricalRule, Dima Hasao region]
-
A.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
C.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
D.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
E.
isHistoricRegionFor
chosen
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 29, 2026, 7:58 p.m.