Triple
T11122465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadamba dynasty |
E263050
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Banavasi |
E267954
|
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: Banavasi | Statement: [Kadamba dynasty, capital, Banavasi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Banavasi Context triple: [Kadamba dynasty, capital, Banavasi]
-
A.
Banavasi
chosen
Banavasi is an ancient town in Karnataka, India, historically significant as an early capital of the Kadamba dynasty and a major center of early Kannada culture and inscriptions.
-
B.
Parbhani
Parbhani is a significant city in the Marathwada region of Maharashtra, India, known as an important commercial and educational center.
-
C.
Yavatmal
Yavatmal is a city in the Indian state of Maharashtra, known as a regional center in the Vidarbha area with a predominantly agrarian economy.
-
D.
Tuljapur
Tuljapur is a town in Maharashtra, India, renowned as a major pilgrimage center for the goddess Bhavani.
-
E.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79afa0ab88190ab6d61df8cf485ec |
completed | April 9, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e441d376f8819080effd5bf29c6bc1 |
completed | April 19, 2026, 2:45 a.m. |
Created at: April 8, 2026, 9:28 p.m.