Triple
T12091768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakinada district |
E287958
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Peddapuram |
E844192
|
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: Peddapuram | Statement: [Kakinada district, hasCity, Peddapuram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peddapuram Context triple: [Kakinada district, hasCity, Peddapuram]
-
A.
Peddapuram
chosen
Peddapuram is a town in the Indian state of Andhra Pradesh known for its historical significance and regional commerce.
-
B.
Nallapadu
Nallapadu is a locality and railway junction near Guntur in Andhra Pradesh, India, serving as a regional rail hub.
-
C.
Banaganapalle
Banaganapalle is a town and legislative assembly constituency in the Nandyal district of Andhra Pradesh, India, known historically for its mangoes and regional political significance.
-
D.
Tadipatri
Tadipatri is a town in the Anantapur district of Andhra Pradesh, India, known for its granite industries and historic temples.
-
E.
Jaggayyapeta
Jaggayyapeta is a town and assembly constituency in the NTR district of Andhra Pradesh, India, known for its historical Buddhist sites and cement industries.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9151797988190b0d007ea806bcf02 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f66d1b44819091f638d2a621ecde |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.