Triple
T27564757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengal Intelligent Park |
E695866
|
entity |
| Predicate | locatedInPlannedTownship |
P82773
|
FINISHED |
| Object | Bidhannagar |
—
|
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: Bidhannagar | Statement: [Bengal Intelligent Park, locatedInPlannedTownship, Bidhannagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPlannedTownship Context triple: [Bengal Intelligent Park, locatedInPlannedTownship, Bidhannagar]
-
A.
locatedInPlannedTown
chosen
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
-
B.
locatedInPlannedCity
Indicates that something is situated within the boundaries of a city that was deliberately designed and planned rather than having developed organically.
-
C.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
D.
locatedInUrbanGrowthBoundary
Indicates that the entity is situated within a designated urban growth boundary area where development is planned or managed.
-
E.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 27, 2026, 1:41 p.m.