Triple

T8663552
Position Surface form Disambiguated ID Type / Status
Subject Aihole temple complex E205606 entity
Predicate locatedIn P40 FINISHED
Object Aihole E205606 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: Aihole | Statement: [Aihole temple complex, locatedIn, Aihole]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aihole
Context triple: [Aihole temple complex, locatedIn, Aihole]
  • A. Belur
    Belur is a locality in the Howrah district of West Bengal, India, known for its proximity to the Hooghly River and the famous Belur Math.
  • B. Belur
    Belur is a historic town in Karnataka, India, renowned for its exquisite Hoysala-era temple architecture, especially the Chennakeshava Temple.
  • C. Aihole temple complex chosen
    The Aihole temple complex is an ancient archaeological site in Karnataka, India, renowned as a cradle of early Chalukyan temple architecture and experimentation in Hindu and Jain rock-cut and structural temples.
  • D. Badami
    Badami is a historic town in Karnataka, India, renowned for its rock-cut cave temples and ancient Chalukyan architecture.
  • E. Hampi
    Hampi is an ancient ruined city in Karnataka, India, famed for its monumental Hindu temples and as the former capital of the Vijayanagara Empire.
  • 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_69ca83516ae88190aefe034b3bc589e3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc489f7edc8190bde1b4dc09249207 completed March 31, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecd0d95ec81908669ee35f0987be7 completed April 2, 2026, 8:09 p.m.
Created at: March 30, 2026, 6:30 p.m.