Triple
T7795630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussain Shahi dynasty |
E180291
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Lakhnauti |
E689717
|
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: Lakhnauti | Statement: [Hussain Shahi dynasty, capital, Lakhnauti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lakhnauti Context triple: [Hussain Shahi dynasty, capital, Lakhnauti]
-
A.
Lakhnauti
chosen
Lakhnauti is the medieval name of the historic city of Gaur, a major political and cultural center of the Bengal Sultanate in eastern India.
-
B.
Rampurhat
Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
-
C.
Adityapur
Adityapur is a major industrial township in Jharkhand, India, known for its large concentration of manufacturing and engineering units.
-
D.
Sultanganj
Sultanganj is a town in Bihar, India, known as a significant Hindu pilgrimage site on the banks of the Ganges River.
-
E.
Krishnanagar
Krishnanagar is a historic town in eastern India known for its cultural heritage, temples, and traditional clay artistry.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae94c41408190b73e37c0ff2c6628 |
completed | March 30, 2026, 9:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc55d5650c8190862d89d1dcc488b4 |
completed | March 31, 2026, 11:16 p.m. |
Created at: March 30, 2026, 4:31 p.m.