Triple
T6564458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bihar |
E153866
|
entity |
| Predicate | hasMajorCity |
P316
|
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: [North Bihar, hasMajorCity, Begusarai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Begusarai Context triple: [North Bihar, hasMajorCity, 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.
Sainthia
Sainthia is a town in the Birbhum district of West Bengal, India, known as a local commercial and cultural center.
-
D.
Giridih
Giridih is a city in eastern India known for its coal and mica mining, situated in the Giridih district of the state of Jharkhand.
-
E.
Chalisgaon
Chalisgaon is a town in the Indian state of Maharashtra known for its railway junction and proximity to historical and religious sites.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae3b9ec8819080f3052556d95810 |
completed | March 27, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7422f57848190901b31229825b9e2 |
completed | March 28, 2026, 2:51 a.m. |
Created at: March 27, 2026, 1:52 p.m.