Triple
T7044970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pattadakal |
E163608
|
entity |
| Predicate | nearbySite |
P350
|
FINISHED |
| Object | Badami |
E201601
|
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: Badami | Statement: [Pattadakal, nearbySite, Badami]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Badami Context triple: [Pattadakal, nearbySite, Badami]
-
A.
Badami
chosen
Badami is a historic town in Karnataka, India, renowned for its rock-cut cave temples and ancient Chalukyan architecture.
-
B.
Dahanapura
Dahanapura was the principal city and political center of the historical Kediri Kingdom in Java.
-
C.
Pachora
Pachora is a town in the Jalgaon district of Maharashtra, India, known as a local commercial and agricultural center in the region.
-
D.
Tamralipti
Tamralipti was an ancient and prominent port city on the eastern coast of the Indian subcontinent that served as a key maritime hub for trade and cultural exchange between India and Southeast Asia.
-
E.
Talagunda
Talagunda is an ancient village in Karnataka, India, renowned for its early Kadamba dynasty inscriptions that are crucial to the study of South Indian history and scripts.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e23730888190a827ca5c61c4eed0 |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7887799f48190b4fa311defd8e9fd |
completed | March 28, 2026, 7:51 a.m. |
Created at: March 27, 2026, 2:37 p.m.