Triple
T14244194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Hills |
E353088
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Madhapur |
E349850
|
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: Madhapur | Statement: [Jubilee Hills, adjacentTo, Madhapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Madhapur Context triple: [Jubilee Hills, adjacentTo, Madhapur]
-
A.
Madhapur
chosen
Madhapur is a major IT and business district in Hyderabad, India, known for its technology parks, corporate offices, and modern urban infrastructure.
-
B.
Damoh
Damoh is a city in central India that serves as the administrative headquarters of Damoh district in the state of Madhya Pradesh.
-
C.
Padampur
Padampur is a town in the Ganganagar district of Rajasthan, India, known for its agricultural economy supported by canal irrigation in the arid northwestern region of the state.
-
D.
Jaipuri
Jaipuri is a regional Indo-Aryan language variety spoken in and around Jaipur in the Indian state of Rajasthan.
-
E.
Hanamkonda
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.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6245d6a481909ef665748cd4d64c |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bb7e0ac81909d62993689b56f83 |
completed | May 8, 2026, 3:42 a.m. |
Created at: April 10, 2026, 1:08 a.m.