Triple
T34193950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangareddy |
E877185
|
entity |
| Predicate | hasNearbyITHub |
P51095
|
FINISHED |
| Object | Hyderabad IT corridor |
—
|
NE NERFINISHED |
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: Hyderabad IT corridor | Statement: [Sangareddy, hasNearbyITHub, Hyderabad IT corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyITHub Context triple: [Sangareddy, hasNearbyITHub, Hyderabad IT corridor]
-
A.
hasNeighborhoodHub
Indicates that one place serves as a central local hub or focal point for community activities within a particular neighborhood.
-
B.
isITHubOf
chosen
Indicates that an entity serves as a central location or primary center for IT-related activities, services, or operations for another entity or area.
-
C.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
D.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
-
E.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
- F. None of above.
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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:55 a.m.