Triple
T13053795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIBN |
E327513
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Babatpur |
E328805
|
NE 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: Babatpur | Statement: [VIBN, locatedNear, Babatpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Babatpur Context triple: [VIBN, locatedNear, Babatpur]
-
A.
Babatpur
chosen
Babatpur is a locality near Varanasi in the Indian state of Uttar Pradesh, known primarily for hosting the city’s main airport.
-
B.
Partapur
Partapur is a locality in Meerut district of Uttar Pradesh, India, known for its proximity to the Dr. Bhimrao Ambedkar Airstrip and its growing urban and institutional development.
-
C.
Dubrajpur
Dubrajpur is a small town in the Birbhum district of West Bengal, India, known for its nearby historic temples and distinctive rock formations.
-
D.
Bhatkuli
Bhatkuli is a small town in the Amravati district of Maharashtra, India, known primarily as a local administrative and market center for surrounding rural areas.
-
E.
Rampurhat
Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980bb52d88190b5be12000e27a2c9 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5ff8c308190a40274c68a1c5da3 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:58 p.m.