Triple
T10094463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alampur |
E215826
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Telugu |
E5056
|
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: Telugu | Statement: [Alampur, languageSpoken, Telugu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telugu Context triple: [Alampur, languageSpoken, Telugu]
-
A.
Telugu
chosen
Telugu is a major Dravidian language predominantly spoken in the Indian states of Andhra Pradesh and Telangana, known for its rich literary tradition and classical status.
-
B.
Rayalaseema Telugu
Rayalaseema Telugu is a regional dialect of the Telugu language spoken primarily in the Rayalaseema region of Andhra Pradesh, characterized by distinct phonetic and lexical features.
-
C.
Kannada
Kannada is a major Dravidian language predominantly spoken in the Indian state of Karnataka and surrounding regions, with a rich literary tradition spanning over a millennium.
-
D.
Andhratharhi
Andhratharhi is a town located in the Madhubani district of the Indian state of Bihar.
-
E.
Tamil
Tamil is a classical Dravidian language spoken predominantly in the Indian state of Tamil Nadu and in parts of Sri Lanka, with a rich literary tradition spanning over two millennia.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd0784c288190967d143beca32c4b |
completed | April 2, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b6aecc488190a9af098f687327ed |
completed | April 5, 2026, 7:23 p.m. |
Created at: March 30, 2026, 9:01 p.m.