Triple
T27843828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishing community |
E703759
|
entity |
| Predicate | notableDistricts |
P40057
|
FINISHED |
| Object | Dhemaji district |
—
|
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: Dhemaji district | Statement: [Mishing community, notableDistricts, Dhemaji district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDistricts Context triple: [Mishing community, notableDistricts, Dhemaji district]
-
A.
notableDistrictCovered
Indicates that a place or entity includes within its area a district that is considered notable or significant.
-
B.
notableDistrictConcentration
Indicates that a notable or significant concentration of something (such as people, activities, or features) is present within a particular district.
-
C.
typicalDistricts
Indicates that certain districts are characteristic or representative examples of a larger region, category, or entity.
-
D.
notableCollectionArea
Indicates that an entity is recognized for having a significant or noteworthy collection focused on a particular geographic area or region.
-
E.
notableRegionOfSettlement
chosen
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: April 27, 2026, 6:05 p.m.