Triple
T10932228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singhwara |
E258234
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Darbhanga city |
E850828
|
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: Darbhanga city | Statement: [Singhwara, locatedNear, Darbhanga city]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Darbhanga city Context triple: [Singhwara, locatedNear, Darbhanga city]
-
A.
Darbhanga
chosen
Darbhanga is a major city in the Indian state of Bihar, known as a cultural and educational center of the Mithila region.
-
B.
Adityapur
Adityapur is a major industrial township in Jharkhand, India, known for its large concentration of manufacturing and engineering units.
-
C.
Lakhnauti
Lakhnauti is the medieval name of the historic city of Gaur, a major political and cultural center of the Bengal Sultanate in eastern India.
-
D.
Rampurhat
Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
-
E.
Sultanganj
Sultanganj is a town in Bihar, India, known as a significant Hindu pilgrimage site on the banks of the Ganges River.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770a16cbc8190acd619defed7114c |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6849dbff08190a352eaaea8606bdb |
completed | April 20, 2026, 7:55 p.m. |
Created at: April 8, 2026, 9:23 p.m.