Triple
T14150304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raidurg |
E350660
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Cyberabad IT hub |
E70266
|
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: Cyberabad IT hub | Statement: [Raidurg, partOf, Cyberabad IT hub]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cyberabad IT hub Context triple: [Raidurg, partOf, Cyberabad IT hub]
-
A.
Cyberabad
chosen
Cyberabad is a popular moniker for the technology-driven, IT and software hub aspects of Hyderabad, India.
-
B.
Cybercity Magarpatta
Cybercity Magarpatta is the major IT and business hub within Magarpatta City in Pune, India, housing numerous technology companies and corporate offices.
-
C.
NESCO IT Park
NESCO IT Park is a major commercial and information technology hub in Goregaon, Mumbai, housing numerous corporate offices and tech companies.
-
D.
Cyberpark district
Cyberpark district is a technology-focused urban area that hosts the Cyberpark 3 complex and other innovation-oriented facilities.
-
E.
Pune IT corridor
Pune IT corridor is a major technology and business hub in Pune, India, encompassing key IT parks and corporate campuses such as Hinjawadi IT Park.
- 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_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7e86820819099d6e3d3d4229f0d |
completed | May 7, 2026, 8:36 p.m. |
Created at: April 10, 2026, 12:56 a.m.