Triple
T14163745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazipet Junction |
E351013
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Hanamkonda |
E897715
|
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: Hanamkonda | Statement: [Kazipet Junction, hasNearbyCity, Hanamkonda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanamkonda Context triple: [Kazipet Junction, hasNearbyCity, Hanamkonda]
-
A.
Hanamkonda
chosen
Hanamkonda is a major urban area and historical locality in the Indian state of Telangana, forming part of the tri-city region along with Warangal and Kazipet.
-
B.
Patancheru
Patancheru is a suburban industrial and residential area on the outskirts of Hyderabad, Telangana, known for its manufacturing hubs and strategic location along major transport routes.
-
C.
Bhagyanagaram
Bhagyanagaram is an alternative name historically used for the Indian city of Hyderabad, particularly in Telugu contexts.
-
D.
Kondapur
Kondapur is a rapidly developing residential and commercial suburb in Hyderabad, India, known for its proximity to major IT hubs and tech parks.
-
E.
Tadipatri
Tadipatri is a town in the Anantapur district of Andhra Pradesh, India, known for its granite industries and historic temples.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de613a4a2081908fd51bf4b4d82b6c |
completed | April 14, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd54fe6b048190a16695af6e269e86 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 12:59 a.m.