Triple
T12895187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Begusarai district |
E308474
|
entity |
| Predicate | headquarters |
P62
|
FINISHED |
| Object | Begusarai |
E303830
|
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: Begusarai | Statement: [Begusarai district, headquarters, Begusarai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Begusarai Context triple: [Begusarai district, headquarters, Begusarai]
-
A.
Begusarai
chosen
Begusarai is an industrial and agricultural city in the Indian state of Bihar, known for its oil refinery and role as a regional commercial hub.
-
B.
Rampurhat
Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
-
C.
Gobardanga
Gobardanga is a town in the Indian state of West Bengal known for its suburban character and connectivity to Kolkata via the Sealdah–Bangaon railway line.
-
D.
Ranaghat
Ranaghat is a prominent town in the Indian state of West Bengal, known as a key railway junction and commercial center in the Nadia region.
-
E.
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.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8cec96c819089d253162bc4705a |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:40 p.m.