Triple
T3357983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HITEC City |
E70649
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Kondapur |
E350659
|
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: Kondapur | Statement: [HITEC City, adjacentTo, Kondapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kondapur Context triple: [HITEC City, adjacentTo, Kondapur]
-
A.
Kondapur
chosen
Kondapur is a rapidly developing residential and commercial suburb in Hyderabad, India, known for its proximity to major IT hubs and tech parks.
-
B.
Guntur
Guntur is a major city in the Indian state of Andhra Pradesh, known historically as an important administrative and commercial center in southeastern India.
-
C.
Bhadrachalam
Bhadrachalam is a temple town in Telangana, India, renowned for its major Sri Rama temple and its location along the banks of the Godavari River.
-
D.
Kakinada
Kakinada is a coastal city in the Indian state of Andhra Pradesh, known for its port, seafood industry, and role as a regional commercial hub.
-
E.
Bhimnagar
Bhimnagar is a settlement in the Indian state of Bihar known for its proximity to the Kosi River and the major Kosi Barrage infrastructure.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb244435c81908e35d2aa36ec4f46 |
completed | March 8, 2026, 5:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3545ea1b08190ad84b7e5f70b4d2e |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:13 p.m.