Triple
T36760202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karimnagar Rural mandal |
E908173
|
entity |
| Predicate | surroundingUrbanCentre |
P54981
|
FINISHED |
| Object | Karimnagar |
—
|
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: Karimnagar | Statement: [Karimnagar Rural mandal, surroundingUrbanCentre, Karimnagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surroundingUrbanCentre Context triple: [Karimnagar Rural mandal, surroundingUrbanCentre, Karimnagar]
-
A.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
isUrbanCentreFor
chosen
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
C.
withinUrbanArea
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
D.
relatedUrbanArea
Indicates that one urban area is geographically or functionally associated with another urban area, such as being nearby, connected, or part of the same broader metropolitan context.
-
E.
connectsToUrbanCenter
Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.