Triple
T9686384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adil Shahi dynasty |
E234418
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Bijapur |
E461984
|
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: Bijapur | Statement: [Adil Shahi dynasty, capital, Bijapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bijapur Context triple: [Adil Shahi dynasty, capital, Bijapur]
-
A.
Bijapur
chosen
Bijapur is a historic city in the Indian state of Karnataka, renowned for its rich Islamic architecture and monuments from the medieval Deccan period.
-
B.
Bidar
Bidar is a historic city in the Indian state of Karnataka, renowned for its medieval fort, rich Deccan Sultanate heritage, and distinctive Bidri metalwork.
-
C.
Ahmednagar
Ahmednagar is a historic city in the Indian state of Maharashtra, known for its medieval forts, Mughal-era significance, and role in the Deccan region’s political history.
-
D.
Belgaum
Belgaum is a major city in the Indian state of Karnataka, known as an important commercial, industrial, and military hub near the Maharashtra–Goa border.
-
E.
Yadgir
Yadgir is a district in the Indian state of Karnataka, known for its agricultural economy and historical forts and temples.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd2dab481908e0d3fed28de9d40 |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c40329448190bccac60a20dcb9d1 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:16 p.m.