Triple
T25560788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshtala |
E640706
|
entity |
| Predicate | residentialGrowth |
P140126
|
FINISHED |
| Object | housing estates |
—
|
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: housing estates | Statement: [Maheshtala, residentialGrowth, housing estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialGrowth Context triple: [Maheshtala, residentialGrowth, housing estates]
-
A.
hasSuburbanGrowth
Indicates that an area or entity is experiencing or characterized by expansion or development typical of suburban environments.
-
B.
residentialCommunity
chosen
Indicates that an entity is a residential community where people live, such as a neighborhood, housing complex, or similar residential area.
-
C.
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.
-
D.
hasUrbanGrowthCharacteristic
Indicates that an entity exhibits a particular quality, pattern, or feature related to urban growth or expansion.
-
E.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 3:46 p.m.