Triple
T4762835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhojpur district |
E105736
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Bhojpur |
E105736
|
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: Bhojpur | Statement: [Bhojpur district, alsoKnownAs, Bhojpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhojpur Context triple: [Bhojpur district, alsoKnownAs, Bhojpur]
-
A.
Bhojpur district
chosen
Bhojpur district is an administrative region in the Indian state of Bihar, historically significant as the birthplace of the 19th-century freedom fighter Kunwar Singh.
-
B.
Burhanpur
Burhanpur is a historic city in central India known for its Mughal-era architecture and strategic location on the banks of the Tapti River.
-
C.
Chhatarpur
Chhatarpur is a city in central India known as an administrative and commercial center in the Bundelkhand region of Madhya Pradesh.
-
D.
Saharsa
Saharsa is a city in the northeastern Indian state of Bihar, known as a major agricultural and commercial center in the Kosi river region.
-
E.
Samastipur
Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd651091cc81909b835439c85e842f |
completed | March 20, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a81c9dc8190b9e7f399ac1de268 |
completed | March 21, 2026, 6:28 a.m. |
Created at: March 20, 2026, 1:20 p.m.