Triple
T34193931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangareddy |
E877185
|
entity |
| Predicate | distanceToHyderabadApproxKm |
—
|
GENERATED |
| Object | 50 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHyderabadApproxKm Context triple: [Sangareddy, distanceToHyderabadApproxKm, 50]
-
A.
distanceToHyderabad
chosen
Indicates the spatial distance between a given entity’s location and the city of Hyderabad.
-
B.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
C.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
-
D.
distanceFromBangalore
Indicates the spatial distance separating a given entity or location from Bangalore.
-
E.
distanceFromVisakhapatnam
Indicates the spatial distance between a given entity and the location of Visakhapatnam.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:55 a.m.