Triple
T26514322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | बारामती विधानसभा मतदारसंघ |
E669770
|
entity |
| Predicate | समाविष्ट_शहर |
P3207
|
FINISHED |
| Object | बारामती |
—
|
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: बारामती | Statement: [बारामती विधानसभा मतदारसंघ, समाविष्ट_शहर, बारामती]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: समाविष्ट_शहर Context triple: [बारामती विधानसभा मतदारसंघ, समाविष्ट_शहर, बारामती]
-
A.
city2
chosen
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
B.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
C.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
-
D.
gatheredCities
Indicates that one entity collected or assembled multiple cities together, typically into a group, list, or shared context.
-
E.
formsUrbanAreaWith
Indicates that two or more settlements are geographically and functionally connected so that together they constitute a single continuous urban area.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61394b50c81909e628b2e5b1aa3d5 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:22 a.m.