Triple
T28458343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodha |
E716778
|
entity |
| Predicate | regionOfConcentrationInWestBengal |
P192362
|
FINISHED |
| Object | Paschim Medinipur district |
—
|
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: Paschim Medinipur district | Statement: [Lodha, regionOfConcentrationInWestBengal, Paschim Medinipur district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfConcentrationInWestBengal Context triple: [Lodha, regionOfConcentrationInWestBengal, Paschim Medinipur district]
-
A.
populationRankInWestBengal
Indicates the relative position of an entity in terms of population size compared to other entities within West Bengal.
-
B.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
C.
distanceFromKolkata
Indicates the spatial distance between a given location and the city of Kolkata.
-
D.
mandalHeadquartersOf
Indicates that a location serves as the administrative headquarters for a specified mandal (sub-district).
-
E.
IndianCenter
Indicates that something serves as a central or primary hub related to India or Indian affairs.
- F. None of above. chosen
Provenance (4 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: April 28, 2026, 1:55 a.m.