Triple
T4141884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharadi |
E89288
|
entity |
| Predicate | urbanCategory |
P749
|
FINISHED |
| Object | emerging IT suburb of Pune |
—
|
LITERAL 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: emerging IT suburb of Pune | Statement: [Kharadi, urbanCategory, emerging IT suburb of Pune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCategory Context triple: [Kharadi, urbanCategory, emerging IT suburb of Pune]
-
A.
urbanComponent
Indicates that something functions as a constituent part or element within an urban area or city system.
-
B.
urbanDevelopment
Indicates the process or activities through which urban areas are planned, expanded, or transformed, including changes to infrastructure, land use, and the built environment.
-
C.
cityWide
Indicates that something applies to, affects, or extends across an entire city.
-
D.
urbanAreaType
chosen
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
E.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.