Triple
T13591046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talacauvery |
E324691
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Kodava Takk |
E1014754
|
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: Kodava Takk | Statement: [Talacauvery, languageSpoken, Kodava Takk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kodava Takk Context triple: [Talacauvery, languageSpoken, Kodava Takk]
-
A.
Kodava Takk
chosen
Kodava Takk is a Dravidian language spoken primarily by the Kodava (Coorg) community in the Kodagu district of Karnataka, India.
-
B.
Kaumodaki Gada
Kaumodaki Gada is the divine mace associated with the Hindu god Vishnu (Narayana), symbolizing his power to protect and uphold cosmic order.
-
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.
Hogenakkal
Hogenakkal is a small town in Tamil Nadu, India, known as the gateway to the famous Hogenakkal Falls on the Kaveri River.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bc578908190abd5cca94b1c3a5c |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.