Triple
T19018791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapashera |
E465426
|
entity |
| Predicate | nearbyLocality |
P4647
|
FINISHED |
| Object | Mahipalpur |
—
|
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: Mahipalpur | Statement: [Kapashera, nearbyLocality, Mahipalpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mahipalpur Context triple: [Kapashera, nearbyLocality, Mahipalpur]
-
A.
Mahipalpur
chosen
Mahipalpur is an urban village and commercial area in Delhi, India, located near Indira Gandhi International Airport and known for its hotels, transport hubs, and proximity to major highways.
-
B.
Jagdishpur
Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
-
C.
Jagdishpur
Jagdishpur is a town in the Amethi district of Uttar Pradesh, India, known for its industrial area and historical significance in the region.
-
D.
Jaisinghpur
Jaisinghpur is a town located in the Sultanpur district of the Indian state of Uttar Pradesh.
-
E.
Vikrampur
Vikrampur was a historic urban and political center in the Bengal region, renowned as an important seat of power and culture in medieval South Asia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dd0e6c8190a6dc6af1f7901299 |
completed | April 20, 2026, 7:33 a.m. |
Created at: April 10, 2026, 12:02 p.m.