Triple
T19079604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Bihar |
E466990
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Sasaram |
—
|
NE NERFINISHED |
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: Sasaram | Statement: [Western Bihar, majorCity, Sasaram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sasaram Context triple: [Western Bihar, majorCity, Sasaram]
-
A.
Sasaram
chosen
Sasaram is a historic town in eastern India known for its grand Mughal-era monuments, especially the tomb of Sher Shah Suri.
-
B.
Hajipur
Hajipur is a prominent city in the Indian state of Bihar, known as an important railway and commercial hub located near the state capital, Patna.
-
C.
Saharanpur
Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
-
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 (2 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e82ec08190873186ff51e89d86 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 10, 2026, 12:04 p.m.