Triple
T7660830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolami |
E173499
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Northwestern Kolami |
E173499
|
NE 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: Northwestern Kolami | Statement: [Kolami, hasDialects, Northwestern Kolami]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Northwestern Kolami Context triple: [Kolami, hasDialects, Northwestern Kolami]
-
A.
Kolami
chosen
Kolami is a Dravidian language spoken primarily by the Kolam tribal communities in central India, especially in parts of Maharashtra and Telangana.
-
B.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
C.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
D.
Bagheli
Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
-
E.
Gōṇḍī
Gōṇḍī is a South-Central Dravidian language spoken primarily by the Gondi people in central India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c701a47a5c8190867e39f552c86787 |
completed | March 27, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89b14b6848190892a262903d78b79 |
completed | March 29, 2026, 3:23 a.m. |
Created at: March 27, 2026, 3:59 p.m.