Triple
T19410087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boudh district |
E485563
|
entity |
| Predicate | hasTribalCommunity |
P17132
|
FINISHED |
| Object | Kandha |
—
|
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: Kandha | Statement: [Boudh district, hasTribalCommunity, Kandha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kandha Context triple: [Boudh district, hasTribalCommunity, Kandha]
-
A.
Kandha
chosen
The Kandha are an indigenous tribal community of eastern India, primarily in Odisha, known for their distinct language, traditional agrarian lifestyle, and rich ritual and festival practices.
-
B.
Kandava
Kandava is a small historic town in western Latvia known for its scenic location in the Kurzeme region and well-preserved old town architecture.
-
C.
Kadaru
Kadaru is a Nubian language spoken by the Kadaru people in parts of Sudan.
-
D.
Kundagannada
Kundagannada is a regional dialect of the Kannada language spoken primarily in the coastal districts of Karnataka, India.
-
E.
Kandas
Kandas is an Oceanic language of the Meso-Melanesian subgroup spoken in parts of Papua New Guinea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af4cc0c81909056b5e2ee574ab1 |
completed | April 20, 2026, 1:32 p.m. |
Created at: April 10, 2026, 1:37 p.m.